This record as markdown: /tools/com-googleapis-memorystore-mcp/delete-backup.md
What delete_backup does on Mcp
AI agents call delete_backup to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Required. Instance backup resource name using the form: `projects/{project_id}/locations/{location_id}/backupCollections/{backup_collection_id}/backups/{backup_ |
requestId | string | — | Optional. Idempotent request UUID. |
Parameters from the server's own tool schema.
Why delete_backup is rated Critical
This tool irreversibly deletes backup data, which cannot be undone. Deletion of backups is a destructive operation with significant blast radius—an AI agent misusing this could permanently lose recovery points for Valkey instances. This is more severe than Write (reversible modifications) and categorizes as Destructive.
From the tool's definition Tool name is 'delete_backup' and description states 'Delete a Memorystore for Valkey backup.' The verb 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_backup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_backup, this is the rule to start with:
delete_backup is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every delete_backup call is checked against it from then on.
Questions about delete_backup
Delete a Memorystore for Valkey backup. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_backup accepts 2 parameters: name, requestId. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for delete_backup: 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 Mcp. Nothing to install.
delete_backup 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 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. 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 is provided by the MCP server (https://memorystore.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue