delete_observations

Delete specific observations from entities

Server Knowledge Graph MCP Server yuchoe/knowledge-graph-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_observations does on Knowledge Graph MCP Server

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

Why delete_observations needs a policy

Deleting observations from a knowledge graph is an irreversible data destruction operation. Once deleted, observations cannot be recovered through the tool's normal read operations. The blast radius is high because an AI agent misusing this tool could permanently erase critical structured information, relationships, and time-based data that may be essential to downstream decision-making or auditing.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete specific observations from entities'. The delete_* functions in the tool list (delete_entities, delete_relations) are definitionally destructive operations that remove data irreversibly.

Questions about delete_observations

What does the delete_observations tool do? +

Delete specific observations from entities. It is categorised as a Destructive tool in the Knowledge Graph MCP 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 delete_observations? +

Register the Knowledge Graph MCP 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 Knowledge Graph MCP Server. Nothing to install.

What risk level is delete_observations? +

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 delete_observations? +

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.

How do I block delete_observations completely? +

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.

What MCP server provides delete_observations? +

delete_observations is provided by the Knowledge Graph MCP Server MCP server (yuchoe/knowledge-graph-mcp-server). 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.