Remove a trust boundary. Creates a new model version.
AI agents call remove_trust_boundary to permanently remove resources in Mipiti MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a trust boundary is a destructive action that permanently deletes a security architecture element. While a new model version is created (suggesting some versioning), the act of removing a trust boundary from a threat model is irreversible in the sense that it alters the security posture definition.
From the tool's definition 'Remove a trust boundary. Creates a new model version.' - 'remove' indicates irreversible deletion of a trust boundary element from the security model.
Attacks that exploit this kind of access
Remove a trust boundary. Creates a new model version. It is categorised as a Destructive tool in the Mipiti MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for remove_trust_boundary: 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.
remove_trust_boundary is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_trust_boundary 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 remove_trust_boundary. 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.
remove_trust_boundary 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 →