コンテキストを変更します (create/update/delete/move)
AI agents call mutate_context to permanently remove resources in OCD - Organized Context Datastore (MCP) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool also performs reversible operations (create, update, move), the inclusion of delete capability elevates it to Destructive category per the rule: 'When a tool spans categories, pick the most severe applicable.' Deletion of persistent project knowledge stored in a hierarchical datastore represents irreversible data loss with high blast radius if misused by an AI agent.
From the tool's definition Tool description states it can perform create/update/delete/move operations on contexts. The explicit mention of 'delete' makes this a destructive operation—deletion of structured data/Markdown files from persistent storage cannot be undone.
Attacks that exploit this kind of access
コンテキストを変更します (create/update/delete/move). It is categorised as a Destructive tool in the OCD - Organized Context Datastore (MCP) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OCD - Organized Context Datastore (MCP) MCP server in PolicyLayer and add a rule for mutate_context: 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 OCD - Organized Context Datastore (MCP). Nothing to install.
mutate_context 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 mutate_context 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 mutate_context. 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.
mutate_context is provided by the OCD - Organized Context Datastore (MCP) MCP server (teamstove/organized-context-datastore-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 →