# \[Feature Request\] MCP tool for creating/updating Action Types **URL:** \ **Category:** Product Feedback\ **Tags:** foundry-mcp\ **Created:** [December 16, 2025, 9:11am UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694 "2025-12-16T09:11:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ujjalb](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/ujjalb/32/6412_2.png) [@ujjalb](https://community.palantir.com/u/ujjalb)\ **Post date:** [December 16, 2025, 9:11am UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694/1 "2025-12-16T09:11:02Z")
Currently, MCP provides tools for creating/updating Object Types (create\_or\_update\_foundry\_object\_type) and Link Types (create\_or\_update\_foundry\_link\_type), but there is no equivalent tool for Action Types. Current Behavior: - When an Object Type is created, Foundry auto-generates CRUD actions (create/modify/delete) - These auto-generated actions do NOT update when new properties are added to the Object Type - Custom action types defined in configuration cannot be created via MCP - The only way to update action type parameters is through the Foundry UI Use Case: We manage our ontology as code using a JSON config file + Python script. We define: - Object Types (works via MCP) - Link Types (works via MCP) - Action Types (no MCP support) When adding an editOnly property to an Object Type, we need to also add it as a parameter to the corresponding Action Type. Without MCP support, this breaks the “ontology as code” workflow. Requested Feature: create\_or\_update\_foundry\_action\_type MCP tool with ability to: - Add/remove parameters to existing action types - Create custom action types (beyond auto-generated CRUD) ---
**Author:** ![Andrius](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@Andrius](https://community.palantir.com/u/Andrius)\ **Post date:** [December 18, 2025, 4:40pm UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694/2 "2025-12-18T16:40:45Z")
👋 Hey, We’ll treat adding a `create_or_update_action_type` tool as a high priority in the new year. Out of curiosity could you share more details about your setup? ---
**Author:** ![Olek](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/olek/32/6775_2.png) [@Olek](https://community.palantir.com/u/Olek)\ **Post date:** [January 24, 2026, 12:23am UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694/3 "2026-01-24T00:23:33Z")
Hello @Andrius The _ **get\_foundry\_ontology\_rid** _ tool has a “list all” mode when no parameters are provided, but there’s no equivalent list\_all\_projects or search\_projects tool. To browse projects, you’d need to either: - Already know a project RID - Have a local Foundry repo cloned (then get\_repository\_context can extract the project RID from it) - Get a RID from Foundry’s web UI Problem it creates: Most users unfamiliar with ontology concepts will start with natural questions like: - “What are my projects?” - “Show me my datasets” - “What do I have in Foundry?” These are the obvious entry points. Without a list\_projects tool, the MCP cannot answer these basic questions and the conversation stalls. Users are forced to manually find RIDs in the Foundry UI. Proposed solution: Add a list\_foundry\_projects tool that: - Lists all projects accessible to the authenticated user - Supports optional query filter for name search - Returns project RIDs, names, and paths - Supports pagination Thank you! ---
**Author:** ![Olek](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/olek/32/6775_2.png) [@Olek](https://community.palantir.com/u/Olek)\ **Post date:** [January 26, 2026, 8:18am UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694/4 "2026-01-26T08:18:39Z")
The **search\_foundry\_ontology** MCP tool cannot list all object types or action types in an ontology because it requires a non-empty search string. Current behavior: - Searching with “contains”: “” returns error: “string must be non empty” - Users must guess at object/action type names to search Expected behavior: - Ability to list all object types or action types without knowing their names beforehand Suggested solutions: 1. Add a “type”: “matchAll” query option (similar to search\_foundry\_functions) 2. Allow empty string in contains to match all 3. Add dedicated list\_object\_types / list\_action\_types tools Use case: When a user asks “what objects do I have in my ontology?” there’s currently no way to answer this without guessing names. This is a common discovery/exploration scenario. ---
**Author:** ![Andrius](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@Andrius](https://community.palantir.com/u/Andrius)\ **Post date:** [February 19, 2026, 12:54pm UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694/5 "2026-02-19T12:54:25Z")
Palantir MCP now ships with Action type management tools. The MCP can create actions to modify objects and links. The MCP cannot yet create actions that trigger functions. Please let us know if that would be useful as well. ---
**Author:** ![Olek](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/olek/32/6775_2.png) [@Olek](https://community.palantir.com/u/Olek)\ **Post date:** [February 19, 2026, 6:19pm UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694/6 "2026-02-19T18:19:19Z")
Great to see the new action type management tools in the latest MCP update! . These solve real discovery and ontology management gaps. Thank you for listening to community feedback 🙌 Two requests: 1. Actions that trigger functions — YES, absolutely useful. 2. Agent Lifecycle — the missing piece The MCP now covers the full ontology lifecycle: ✅ Object types (create/update/delete) ✅ Link types (create/update/delete) ✅ Action types (create/update/delete) — **new!** ✅ Datasets (create/write/query) ✅ Branches & proposals ✅ Projects (search/create) — **new!** But there’s one major gap: **AIP Agent lifecycle.** There’s currently no way to programmatically: - Create an AIP agent - Configure its prompt, tools, and model - Publish a version - Create a session and chat with it I have validated that this is possible through the Platform APIs (`/aip-agents/api/agents/create`, `/save`, `/publish` and the v2 sessions API). I have built a working prototype that creates an agent, configures it with tools and, publishes it, and chats with it — all programmatically, zero UI. **Proposed MCP tools:** | Tool | What it does | | --- | --- | | `create_foundry_agent` | Create an AIP agent in a folder (by RID or path) | | `configure_foundry_agent` | Set prompt, model, and tools (auto-discovers action RIDs by object type name) | | `publish_foundry_agent` | Publish a versioned release | | `chat_foundry_agent` | Create session + send message | | `list_foundry_agents` | List agents in a folder | **Why this matters:** With these tools, the full zero-to-agent pipeline becomes possible entirely through MCP: 1. `create_foundry_project` → set up project 2. `create_and_write_to_foundry_dataset` → upload data 3. `create_or_update_foundry_object_type` → define ontology 4. `create_or_update_foundry_action_type` → wire up actions 5. **`create_foundry_agent`** → build the agent with those tools 6. **`configure_foundry_agent`** → set prompt + attach ontology tools 7. **`publish_foundry_agent`** → deploy That’s the complete pipeline from raw data to a working agent. ---
**Author:** ![ujjalb](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/ujjalb/32/6412_2.png) [@ujjalb](https://community.palantir.com/u/ujjalb)\ **Post date:** [February 23, 2026, 2:27pm UTC](https://community.palantir.com/t/feature-request-mcp-tool-for-creating-updating-action-types/5694/7 "2026-02-23T14:27:10Z")
thanks so much for the update. very useful to manage ontology as a code.