delete_blob

THE RISK

Critical Risk

Why delete_blob needs a policy

This tool permanently removes objects from Google Cloud Storage without the ability to undo the operation (unless backups exist outside this tool's scope). Deletion of cloud storage objects is irreversible and represents data loss.

From the tool's definition Tool name is 'delete_blob' with description 'Delete a blob from a bucket.' The verb 'Delete' indicates irreversible removal of data from cloud storage.

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

POLICY

How to control delete_blob

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

policy.json

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

delete_blob 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 Gcp Storage — 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 Gcp Storage tools

Destructive batch_delete Delete multiple blobs from a bucket. Destructive delete_bucket Delete a GCS bucket. Write batch_upload Upload multiple files to a bucket. Write copy_blob Copy a blob from one location to another. Write create_bucket Create a new GCS bucket. Write move_blob Move a blob from one location to another. Write upload_blob Upload a file to a bucket as a blob. Read blob_exists Check if a blob exists.

All 23 Gcp Storage 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 Gcp Storage → 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 delete_blob

What does the delete_blob tool do? +

Delete a blob from a bucket. It is categorised as a Destructive tool in the Gcp Storage 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 delete_blob? +

Register the Gcp Storage MCP server in PolicyLayer and add a rule for delete_blob: 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 Gcp Storage. Nothing to install.

What risk level is delete_blob? +

delete_blob 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 delete_blob? +

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

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

delete_blob is provided by the Gcp Storage MCP server (uysalserkan/gcp-storage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gcp Storage tool call.

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

CHECK YOUR STACK →