# delete_instance

Delete a Memorystore for Valkey instance.

Agent View of the PolicyLayer registry record for `delete_instance`. HTML page: https://policylayer.com/tools/com-googleapis-memorystore-mcp/delete-instance

## Facts

- Tool: `delete_instance`
- Server: Mcp (`https://memorystore.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-memorystore-mcp.md
- Homepage: https://github.com/https://memorystore.googleapis.com/mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | yes | Required. The name of the instance to delete. Format: projects/{project}/locations/{location}/instances/{instance} |
| `requestId` | string | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_instance",
    "arguments": {
      "name": "<name>"
    }
  }
}
```

## 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 own definition: "Tool name 'delete_instance' combined with description 'Delete a Memorystore for Valkey instance' explicitly performs irreversible deletion of a data storage instance."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_instance"
  ]
}
```

## Other tools on Mcp (13)

- `delete_backup` — Destructive — https://policylayer.com/tools/com-googleapis-memorystore-mcp/delete-backup.md
- `get_backup` — Read — https://policylayer.com/tools/com-googleapis-memorystore-mcp/get-backup.md
- `get_backup_collection` — Read — https://policylayer.com/tools/com-googleapis-memorystore-mcp/get-backup-collection.md
- `get_certificate_authority` — Read — https://policylayer.com/tools/com-googleapis-memorystore-mcp/get-certificate-authority.md
- `get_instance` — Read — https://policylayer.com/tools/com-googleapis-memorystore-mcp/get-instance.md
- `list_backup_collections` — Read — https://policylayer.com/tools/com-googleapis-memorystore-mcp/list-backup-collections.md
- `list_backups` — Read — https://policylayer.com/tools/com-googleapis-memorystore-mcp/list-backups.md
- `list_instances` — Read — https://policylayer.com/tools/com-googleapis-memorystore-mcp/list-instances.md
- `backup_instance` — Write — https://policylayer.com/tools/com-googleapis-memorystore-mcp/backup-instance.md
- `create_instance` — Write — https://policylayer.com/tools/com-googleapis-memorystore-mcp/create-instance.md
- `export_backup` — Write — https://policylayer.com/tools/com-googleapis-memorystore-mcp/export-backup.md
- `reschedule_maintenance` — Write — https://policylayer.com/tools/com-googleapis-memorystore-mcp/reschedule-maintenance.md
- `update_instance` — Write — https://policylayer.com/tools/com-googleapis-memorystore-mcp/update-instance.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-googleapis-memorystore-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-memorystore-mcp