delete_observations
Delete specific observations from entities
This record as markdown: /tools/danielsimonjr-memory-mcp/delete-observations.md
What delete_observations does on Enhanced Knowledge Graph Memory Server
AI agents call delete_observations to permanently remove resources in Enhanced Knowledge Graph Memory Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_observations is rated Critical
This tool permanently removes observations from the knowledge graph storage. Deletion cannot be undone and represents irreversible data loss. While the scope is limited to observations within entities (not the entire database), it still qualifies as Destructive rather than Write because the operation cannot be reversed.
From the tool's definition Tool name is 'delete_observations' and description states 'Delete specific observations from entities'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_observations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_observations, this is the rule to start with:
delete_observations is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every delete_observations call is checked against it from then on.
Questions about delete_observations
Delete specific observations from entities. It is categorised as a Destructive tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
delete_observations is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
delete_observations is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
This server
Across the catalogue