AI agents call batch_delete to permanently remove resources in Gcp Storage — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from Google Cloud Storage without possibility of reversal. Destructive is the correct category as it performs irreversible deletion operations. Severity is high because a misconfigured agent could delete large volumes of critical data; marked high rather than critical because the scope is limited to a single bucket's blobs (not account-wide or cross-service destruction).
From the tool's definition Tool name 'batch_delete' and description 'Delete multiple blobs from a bucket' explicitly indicate irreversible deletion of data. The batch nature amplifies the blast radius by allowing mass deletion in a single operation.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_delete gives an agent:
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 batch_delete:
{
"version": "1",
"default": "deny",
"hide": [
"batch_delete"
]
}batch_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete multiple blobs 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.
Register the Gcp Storage MCP server in PolicyLayer and add a rule for batch_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 Gcp Storage. Nothing to install.
batch_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 batch_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 batch_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.
batch_delete 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.
Start from Gcp Storage, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Gcp Storage tools catalogued and risk-classified — across an index of 43,000+ MCP servers.