Deletes a bucket.
AI agents call delete_bucket to permanently remove resources in Storage — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a bucket is a destructive operation that cannot be undone—all data within the bucket is lost. This has the highest severity impact on data integrity and availability. The action is irreversible and could result in complete loss of stored data, justifying 'critical' severity and placement in the Destructive category over Execute or Write.
From the tool's definition Tool name 'delete_bucket' and description 'Deletes a bucket.' indicate irreversible deletion of cloud storage. Bucket deletion removes all contained objects and metadata permanently.
Attacks that exploit this kind of access
Deletes a bucket. It is categorised as a Destructive tool in the Storage MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Storage MCP server in PolicyLayer and add a rule for delete_bucket: 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 Storage. Nothing to install.
delete_bucket 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 delete_bucket 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 delete_bucket. 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.
delete_bucket is provided by the Storage MCP server (@google-cloud/storage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.