mcp_memory_delete_observations

Delete specific observations from entities in the knowledge graph

Server MCP Memory Server jessefreitas/mcp_memory
Category Destructive
Risk class Critical
Parameters 00 required

What mcp_memory_delete_observations does on MCP Memory Server

AI agents call mcp_memory_delete_observations to permanently remove resources in MCP Memory Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why mcp_memory_delete_observations needs a policy

Deletion of observations from a persistent knowledge graph is an irreversible operation that cannot be undone. While the blast radius is somewhat contained (affects only specific observations rather than entire entities or the graph), the destructive nature and potential to lose important AI memory context warrants a 'high' severity rating.

From the tool's definition Tool name contains 'delete' and description states 'Delete specific observations from entities'. This irreversibly removes data from the knowledge graph with no undo capability.

Questions about mcp_memory_delete_observations

What does the mcp_memory_delete_observations tool do? +

Delete specific observations from entities in the knowledge graph. It is categorised as a Destructive tool in the MCP Memory Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mcp_memory_delete_observations? +

Register the MCP Memory Server MCP server in PolicyLayer and add a rule for mcp_memory_delete_observations: 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 Memory Server. Nothing to install.

What risk level is mcp_memory_delete_observations? +

mcp_memory_delete_observations is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mcp_memory_delete_observations? +

Yes. Add a rate_limit block to the mcp_memory_delete_observations 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.

How do I block mcp_memory_delete_observations completely? +

Set action: deny in the PolicyLayer policy for mcp_memory_delete_observations. 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.

What MCP server provides mcp_memory_delete_observations? +

mcp_memory_delete_observations is provided by the MCP Memory Server MCP server (jessefreitas/mcp_memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.