[Feature Request] MCP tool for creating/updating Action Types

Product Feedback
1

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)
2

:waving_hand: 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?

4 Likes
3

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!

4

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.

5

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.

2 Likes
6

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 :raising_hands:

Two requests:

  1. Actions that trigger functions — YES, absolutely useful.
  2. Agent Lifecycle — the missing piece

The MCP now covers the full ontology lifecycle:
:white_check_mark: Object types (create/update/delete)
:white_check_mark: Link types (create/update/delete)
:white_check_mark: Action types (create/update/delete) — new!
:white_check_mark: Datasets (create/write/query)
:white_check_mark: Branches & proposals
:white_check_mark: 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.

7

thanks so much for the update. very useful to manage ontology as a code.