STORE: delete a stored document by id, scoped to YOUR wallet.
AI agents call store.doc-delete to permanently remove resources in Mcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of stored documents cannot be undone and represents permanent loss of data. While scoped to the caller's own wallet (limiting blast radius to their own assets), the irreversible nature of document deletion places this in the Destructive category rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'delete a stored document by id' — this is an irreversible data destruction operation scoped to the user's wallet.
Attacks that exploit this kind of access
STORE: delete a stored document by id, scoped to YOUR wallet. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP server in PolicyLayer and add a rule for store.doc-delete: 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 Mcp. Nothing to install.
store.doc-delete 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 store.doc-delete 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 store.doc-delete. 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.
store.doc-delete is provided by the MCP server (@2sio/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 →