delete_observation
Remove specific observation(s) from entity/entities
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/delete-observation.md
What delete_observation does on Project Guardian MCP
AI agents call delete_observation to permanently remove resources in Project Guardian MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_observation is rated Critical
This tool permanently deletes observations from the knowledge graph database. Deletion is irreversible and cannot be undone through normal operations. While the blast radius is limited to observation records (not entire entities or the full database), the destructive nature and potential to corrupt project memory context in an AI-driven system warrants 'high' severity.
From the tool's definition Tool name is 'delete_observation' with description 'Remove specific observation(s) from entity/entities'. The verb 'Remove' and 'delete' indicate irreversible deletion of data records.
Attacks that exploit this kind of access
The rule that runs delete_observation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_observation, this is the rule to start with:
delete_observation 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 Project Guardian MCP, apply this rule, and every delete_observation call is checked against it from then on.
Questions about delete_observation
Remove specific observation(s) from entity/entities. It is categorised as a Destructive tool in the Project Guardian MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Project Guardian MCP server in PolicyLayer and add a rule for delete_observation: 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 Project Guardian MCP. Nothing to install.
delete_observation 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_observation 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_observation. 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_observation is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
Across the catalogue