store.doc-delete

STORE: delete a stored document by id, scoped to YOUR wallet.

SERVERMcp SOURCE@2sio/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/store.doc-delete.md

WHAT IT DOES

What store.doc-delete does on Mcp

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.

RISK

Why store.doc-delete is rated Critical

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

RECOMMENDED RULE

The rule that runs store.doc-delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store.doc-delete, this is the rule to start with:

store.doc-delete Hidden

store.doc-delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "store.doc-delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every store.doc-delete call is checked against it from then on.

FAQ

Questions about store.doc-delete

What does the store.doc-delete tool do? +

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.

How do I enforce a policy on store.doc-delete? +

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.

What risk level is store.doc-delete? +

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.

Can I rate-limit store.doc-delete? +

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.

How do I block store.doc-delete completely? +

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.

What MCP server provides store.doc-delete? +

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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →