delete_observations

Delete specific observations from entities in the knowledge graph

Server Elastic Brain ZH tocharianou/elastic-brain-zh
Category Destructive
Risk class Critical
Parameters 00 required

What delete_observations does on Elastic Brain ZH

AI agents call delete_observations to permanently remove resources in Elastic Brain ZH — 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

This tool permanently removes observations stored in the Elasticsearch-based memory system. Observations are data entities within a knowledge graph, and deletion is irreversible. Even though the blast radius is narrower than system-wide data loss, deletion of stored knowledge affects the integrity and completeness of the AI's persistent memory, warranting a Destructive classification and high severity.

From the tool's definition Tool name is 'delete_observations' with description 'Delete specific observations from entities in the knowledge graph' — the verb 'Delete' explicitly indicates irreversible removal of data.

Questions about delete_observations

What does the delete_observations tool do? +

Delete specific observations from entities in the knowledge graph. It is categorised as a Destructive tool in the Elastic Brain ZH 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 Elastic Brain ZH 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 Elastic Brain ZH. 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 Elastic Brain ZH MCP server (tocharianou/elastic-brain-zh). 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.