storage_delete

THE RISK

Critical Risk

Why storage_delete needs a policy

This tool performs irreversible deletion of data from cloud storage. While the blast radius is limited to a single item at a time (compared to storage_bulk_delete which could delete multiple items), it still qualifies as Destructive because deletion is irreversible and cannot be undone.

From the tool's definition 'Delete a single item from Crawlbase Cloud Storage by RID' — the verb 'Delete' indicates irreversible removal of data. The tool removes stored items that cannot be recovered through the tool's API.

Documented attack patterns abuse exactly the kind of access storage_delete gives an agent:

POLICY

How to control storage_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Crawlbase MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for storage_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "storage_delete"
  ]
}

storage_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Crawlbase MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Crawlbase MCP tools

Destructive storage_bulk_delete Bulk-delete up to 100 items from Crawlbase Cloud Storage by RID. Irreversible. Read crawl Crawl a URL and return HTML content. Pass store=true to push the result to Crawlbase Cloud Read crawl_markdown Crawl a URL and extract clean markdown content. Pass store=true to persist the original pa Read crawl_screenshot Take a screenshot of a webpage. Pass store=true to persist the underlying HTML page to Clo Read storage_bulk_get Bulk-fetch up to 100 stored items by RID. Bodies are decoded automatically. Default as=met Read storage_count Get the total number of documents in Crawlbase Cloud Storage. Read storage_get Retrieve a single stored page from Crawlbase Cloud Storage by RID or URL. Only works for p Read storage_list List RIDs of pages previously crawled with store=true in Crawlbase Cloud Storage. Supports

All 9 Crawlbase MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Crawlbase MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about storage_delete

What does the storage_delete tool do? +

Delete a single item from Crawlbase Cloud Storage by RID. It is categorised as a Destructive tool in the Crawlbase 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 storage_delete? +

Register the Crawlbase MCP server in PolicyLayer and add a rule for storage_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 Crawlbase MCP. Nothing to install.

What risk level is storage_delete? +

storage_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 storage_delete? +

Yes. Add a rate_limit block to the storage_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 storage_delete completely? +

Set action: deny in the PolicyLayer policy for storage_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 storage_delete? +

storage_delete is provided by the Crawlbase MCP server (crawlbase/crawlbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crawlbase MCP tool call.

Start from Crawlbase MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →