Deletes a backup plan association.
AI agents call delete_backup_plan_association 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.
Deletion of backup plan associations is irreversible and cannot be undone through normal means. While not as critical as deleting actual backups, removing a plan association severs the linkage between a backup plan and its target, preventing future backups and potentially exposing data to loss. This is a destructive operation with moderate blast radius if triggered unintentionally by an AI agent.
From the tool's definition Tool name 'delete_backup_plan_association' explicitly performs deletion. Description states 'Deletes a backup plan association.' The verb 'delete' indicates irreversible removal of data/configuration.
Attacks that exploit this kind of access
Deletes a backup plan association. 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_association: 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_association 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_association 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_association. 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_association 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.