# delete_observation

A destructive tool on the Optimized Memory MCP Server V2 MCP server.

Agent View of the PolicyLayer registry record for `delete_observation`. HTML page: https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/delete-observation

## Facts

- Tool: `delete_observation`
- Server: Optimized Memory MCP Server V2 (`agentwong/optimized-memory-mcp-serverv2`) — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2.md
- Homepage: https://github.com/AgentWong/optimized-memory-mcp-serverv2
- Risk category: Destructive (Critical risk)
- Registry record: grade F, 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_observation",
    "arguments": {}
  }
}
```

## Why delete_observation is rated Critical

The 'delete_' prefix is a strong signal of destructive intent. Although the description is empty, the semantic meaning of 'delete_observation' paired with the server's memory management context indicates the tool permanently removes observations. This is irreversible data loss, making it Destructive rather than Write. Confidence is slightly reduced due to missing description, but the name leaves little ambiguity.

From the tool's own definition: "Tool name 'delete_observation' explicitly indicates irreversible deletion. The server manages memory and observations, so this tool deletes stored observations that cannot be recovered."

## Use case

AI agents call delete_observation to permanently remove resources in Optimized Memory MCP Server V2, 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 Optimized Memory MCP Server V2:

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

## Other tools on Optimized Memory MCP Server V2 (16)

- `delete_entity` — Destructive — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/delete-entity.md
- `delete_relationship` — Destructive — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/delete-relationship.md
- `async_tool` — Other — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/async-tool.md
- `my_tool` — Other — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/my-tool.md
- `tool_with_context` — Other — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/tool-with-context.md
- `analyze_provider` — Read — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/analyze-provider.md
- `search_entities` — Read — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/search-entities.md
- `add_version` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/add-version.md
- `create_entity` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/create-entity.md
- `create_observation` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/create-observation.md
- `create_relationship` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/create-relationship.md
- `register_collection` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/register-collection.md
- `register_provider` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/register-provider.md
- `update_entity` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/update-entity.md
- `update_observation` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/update-observation.md
- `update_relationship` — Write — https://policylayer.com/tools/agentwong-optimized-memory-mcp-serverv2/update-relationship.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=agentwong-optimized-memory-mcp-serverv2 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/agentwong-optimized-memory-mcp-serverv2