# delete_memory

Delete a stored value.

Agent View of the PolicyLayer registry record for `delete_memory`. HTML page: https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/delete-memory

## Facts

- Tool: `delete_memory`
- Server: AI Cortex Storage (`https://memory.aic0rt3x.dev/mcp`) — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp.md
- Homepage: https://github.com/https://memory.aic0rt3x.dev/mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `key` | string | yes | ≤ 255 characters, no '/' |
| `namespace` | string | yes | ≤ 255 characters, no '/' |

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_memory",
    "arguments": {
      "key": "<key>",
      "namespace": "<namespace>"
    }
  }
}
```

## Why delete_memory is rated Critical

This tool permanently removes stored data from persistent cloud memory. Deletion is irreversible and cannot be undone. While the blast radius depends on what memories are targeted, the capability to irreversibly erase AI agent memories—potentially including important context, decisions, or session data—represents a high-severity destructive action.

From the tool's own definition: "Tool name is 'delete_memory' and description states 'Delete a stored value.' The verb 'Delete' combined with operation on persistent cloud memory indicates irreversible removal of data."

## Use case

AI agents call delete_memory to permanently remove resources in AI Cortex Storage, 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 AI Cortex Storage:

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

## Other tools on AI Cortex Storage (14)

- `revoke_api_key` — Destructive — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/revoke-api-key.md
- `settle_balance` — Financial — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/settle-balance.md
- `submit_feature_request` — Financial — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/submit-feature-request.md
- `get_account` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/get-account.md
- `get_memory` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/get-memory.md
- `list_api_keys` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-api-keys.md
- `list_keys` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-keys.md
- `list_namespaces` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-namespaces.md
- `list_payments` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-payments.md
- `search_by_tag` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/search-by-tag.md
- `top_memories` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/top-memories.md
- `create_api_key` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/create-api-key.md
- `put_memory` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/put-memory.md
- `submit_exit_feedback` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/submit-exit-feedback.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=dev-aic0rt3x-memory-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-aic0rt3x-memory-mcp
