コンテキストを削除します (配列対応: 複数一括削除可能)
AI agents call delete_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.
This tool permanently removes stored contexts (data) without possibility of undo. Even though the broader system stores data as Markdown files that might be version-controlled, the tool itself performs irreversible deletion. Destructive is more severe than Write. High severity reflects that an AI agent could lose significant project knowledge or accidentally wipe critical contexts in batch operations.
From the tool's definition Tool name 'delete_context' combined with description indicating deletion capability ('コンテキストを削除します' = 'Delete context'; '複数一括削除可能' = 'can delete multiple in batch'). This irreversibly removes structured memory/Markdown files from the datastore.
Attacks that exploit this kind of access
コンテキストを削除します (配列対応: 複数一括削除可能). 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 delete_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.
delete_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 delete_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 delete_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.
delete_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 →