delete_entity
Delete an entity from the knowledge graph
This record as markdown: /tools/desimpkins-daniel-lightrag-mcp/delete-entity.md
What delete_entity does on Daniel LightRAG MCP Server
AI agents call delete_entity to permanently remove resources in Daniel LightRAG MCP Server, 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
Deletion of knowledge graph entities cannot be undone and represents permanent data loss. While not as critical as financial operations, the irreversible nature and potential cascading effects on dependent relations and queries in the knowledge graph justify 'high' severity. Confidence is high because the intent is unambiguous from both the name and description.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an entity from the knowledge graph' — this is an irreversible removal operation.
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 Daniel LightRAG MCP Server, 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 Daniel LightRAG MCP Server, apply this rule, and every delete_entity call is checked against it from then on.
Questions about delete_entity
Delete an entity from the knowledge graph. It is categorised as a Destructive tool in the Daniel LightRAG MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Daniel LightRAG MCP Server 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 Daniel LightRAG MCP Server. 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 Daniel LightRAG MCP Server MCP server (desimpkins/daniel-lightrag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Daniel LightRAG MCP Server, and thousands of servers like it.
Across the catalogue