Deletes a backup plan.
AI agents call delete_backup_plan 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.
This tool performs an irreversible deletion of a backup plan, which fits the Destructive category definition. The impact is high because deleting backup plans can result in loss of disaster recovery capabilities and data recovery options. The confidence is very high due to explicit use of 'delete' and clear description of destructive intent.
From the tool's definition Tool name contains 'delete' and description states 'Deletes a backup plan.' Deletion of backup plans is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Deletes a backup plan. 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_backup_plan: 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_backup_plan 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_backup_plan 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_backup_plan. 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_backup_plan 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.