Data governance

The Palantir Model Context Protocol (MCP) provides secure integration between AI systems and Foundry resources. The security and data governance policies depend on how and where the MCP is used.

Data flow and security models

Foundry platform

The following data flow and security model applies when using Palantir MCP through Continue in VS Code within the Foundry platform:

• LLM provider: Uses Palantir-provided third party LLMs.
• Data governance: Follows your organization's existing contract with Palantir.
• Data location: All data remains within your Foundry environment.
• Security: Inherits Foundry's security model and controls.

Local environment

The following data flow and security models apply when using Palantir MCP on local machines with third-party AI tools (such as VS Code Copilot, Claude Code, Windsurf, or Cursor):

• LLM provider: Depends on the interface.
  • Claude Code: Data is sent to Anthropic.
  • VS Code Copilot: Data is sent to Microsoft.
  • Other tools: Check the policies of the LLM provider.
• Data flow: MCP tool outputs are sent to the respective LLM provider.
• Data governance: Depends on your contract with the specific LLM provider.

Write access

The Palantir MCP has a limited set of tools you can use to write to or modify your ontology and datasets. We do not provide destructive write tools. All tools that can perform write actions are either non-destructive or require a human to approve the changes.

LLM agents are allowed to create new datasets but are not allowed to update or delete existing datasets.

All ontology modifications (including deletions) must be processed through a proposal; human approval is required to merge changes into your main ontology.