Deletes a specific object.
AI agents call delete_object 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.
The tool permanently removes data from cloud storage with no recovery mechanism built into the tool itself. While GCS may have versioning or backup features available separately (as evidenced by sibling tools like create_backup_plan, create_backup_vault), the delete_object tool itself performs an irreversible action.
From the tool's definition Tool name 'delete_object' explicitly indicates deletion. Description states 'Deletes a specific object.' This is an irreversible operation on stored data in GCS.
Attacks that exploit this kind of access
Deletes a specific object. 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_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 Storage. Nothing to install.
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 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 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.
delete_object 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.