Delete a cross-model reliance edge.
AI agents call delete_reliance 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.
This tool performs an irreversible deletion operation on a reliance relationship within a security threat model. Deleting reliance edges cannot be undone and modifies the integrity of the threat model topology. While the blast radius is constrained to one model artifact, the action is destructive in nature and warrants the 'Destructive' category per the classification rules.
From the tool's definition Tool name 'delete_reliance' paired with description 'Delete a cross-model reliance edge' clearly indicates irreversible deletion of a data element (a reliance edge) from the threat modeling graph.
Attacks that exploit this kind of access
Delete a cross-model reliance edge. 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 delete_reliance: 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.
delete_reliance 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 delete_reliance 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 delete_reliance. 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.
delete_reliance 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 →