attach_foundation
AI agents use attach_foundation to create or update resources in Mipiti MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mipiti MCP Server environment.
The tool name suggests attaching or linking a foundation (likely a security framework, control, or baseline) to an entity in the Mipiti platform. Without a description, exact behavior is unclear, but the naming pattern matches write-oriented sibling tools that create or establish relationships. This is reversible (not Destructive), does not execute external code (not Execute), and does not move money (not Financial).
From the tool's definition Tool name 'attach_foundation' with empty description; sibling tools like 'add_asset', 'add_evidence', 'add_model_to_system' are all Write operations (create/modify) in a security posture platform context.
Attacks that exploit this kind of access
attach_foundation. It is categorised as a Write tool in the Mipiti MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for attach_foundation: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mipiti MCP Server. Nothing to install.
attach_foundation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the attach_foundation rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for attach_foundation. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
attach_foundation is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →