This record as markdown: /tools/com-googleapis-memorystore-mcp/delete-instance.md
What delete_instance does on Mcp
AI agents call delete_instance 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. The name of the instance to delete. Format: projects/{project}/locations/{location}/instances/{instance} |
requestId | string | — | Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the re |
Parameters from the server's own tool schema.
Why delete_instance is rated Critical
Deleting a Memorystore instance is a destructive operation that cannot be undone and results in permanent loss of the instance and its data (unless backups exist). This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The high severity reflects the significant blast radius—an AI agent misusing this tool could destroy production data stores,…
From the tool's definition Tool name 'delete_instance' combined with description 'Delete a Memorystore for Valkey instance' explicitly performs irreversible deletion of a data storage instance.
Attacks that exploit this kind of access
The rule that runs delete_instance 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_instance, this is the rule to start with:
delete_instance 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_instance call is checked against it from then on.
Questions about delete_instance
Delete a Memorystore for Valkey instance. 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_instance 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_instance: 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_instance 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_instance 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_instance. 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_instance 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