delete_entity
Delete entity/entities and their relations from project memory
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/delete-entity.md
What delete_entity does on Project Guardian MCP
AI agents call delete_entity 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_entity is rated Critical
This tool permanently removes entities and associated relations from the knowledge graph without explicit undo capability mentioned. While localized to a single project memory system (not production infrastructure), deletion of core entities could break downstream workflows and analysis. Classified as Destructive rather than Write because the action is irreversible and cannot be undone through normal API operations.
From the tool's definition Tool name is 'delete_entity' and description states 'Delete entity/entities and their relations from project memory' — the verb 'delete' combined with cascade effects on relations indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs delete_entity 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_entity, this is the rule to start with:
delete_entity 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_entity call is checked against it from then on.
Questions about delete_entity
Delete entity/entities and their relations from project memory. 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_entity: 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_entity 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_entity 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_entity. 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_entity 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