# delete_memory

Permanently delete a memory by ID. Use archive_memory instead for soft delete.

Agent View of the PolicyLayer registry record for `delete_memory`. HTML page: https://policylayer.com/tools/0xrelogic-cognio/delete-memory

## Facts

- Tool: `delete_memory`
- Server: Cognio (`0xrelogic/cognio`) — https://policylayer.com/tools/0xrelogic-cognio.md
- Homepage: https://github.com/0xReLogic/Cognio
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why delete_memory is rated Critical

This tool irreversibly deletes data (memory records) and cannot be undone. The description explicitly contrasts it with a reversible alternative (archive_memory), confirming permanent deletion semantics. An AI agent misusing this could erase important contextual information or user data without recovery.

From the tool's own definition: "Tool name is 'delete_memory' and description states 'Permanently delete a memory by ID' with explicit acknowledgment that this is irreversible ('Use archive_memory instead for soft delete')."

## Use case

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

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

## Other tools on Cognio (11)

- `export_memories` — Read — https://policylayer.com/tools/0xrelogic-cognio/export-memories.md
- `get_active_project` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-active-project.md
- `get_memory` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-memory.md
- `get_memory_stats` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-memory-stats.md
- `list_memories` — Read — https://policylayer.com/tools/0xrelogic-cognio/list-memories.md
- `list_projects` — Read — https://policylayer.com/tools/0xrelogic-cognio/list-projects.md
- `search_memory` — Read — https://policylayer.com/tools/0xrelogic-cognio/search-memory.md
- `summarize_text` — Read — https://policylayer.com/tools/0xrelogic-cognio/summarize-text.md
- `archive_memory` — Write — https://policylayer.com/tools/0xrelogic-cognio/archive-memory.md
- `save_memory` — Write — https://policylayer.com/tools/0xrelogic-cognio/save-memory.md
- `set_active_project` — Write — https://policylayer.com/tools/0xrelogic-cognio/set-active-project.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=0xrelogic-cognio · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xrelogic-cognio