Delete an object from Cloud Storage bucket
AI agents call storage_delete_object to permanently remove resources in Google Cloud — 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 Cloud Storage without possibility of recovery (unless backups exist outside the tool's control). Deletion is an irreversible operation that cannot be undone through the tool itself.
From the tool's definition Tool name 'storage_delete_object' combined with description 'Delete an object from Cloud Storage bucket' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete an object from Cloud Storage bucket. It is categorised as a Destructive tool in the Google Cloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Cloud MCP server in PolicyLayer and add a rule for storage_delete_object: 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 Google Cloud. Nothing to install.
storage_delete_object 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 storage_delete_object 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 storage_delete_object. 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.
storage_delete_object is provided by the Google Cloud MCP server (lockon-n/google-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →