remove_assumption
AI agents call remove_assumption 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.
The 'remove_' prefix strongly suggests irreversible deletion of an assumption from the threat model. Given the sibling tool 'add_assumption' exists for creation, this tool likely handles the inverse operation (deletion). Removing assumptions from a security threat model could have significant impact on the integrity of compliance mappings and security posture assessments.
From the tool's definition Tool name 'remove_assumption' implies deletion of an assumption record; description is empty and uninformative.
Attacks that exploit this kind of access
remove_assumption. 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_assumption: 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_assumption 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_assumption 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_assumption. 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_assumption 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 →