New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_entity

Delete an entity from the knowledge graph

SERVERDaniel LightRAG MCP Server SOURCEdesimpkins/daniel-lightrag-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_entity

What does the delete_entity tool do? +

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.

How do I enforce a policy on delete_entity? +

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.

What risk level is delete_entity? +

delete_entity 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_entity? +

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.

How do I block delete_entity completely? +

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.

What MCP server provides delete_entity? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Daniel LightRAG MCP Server's. Pull the full record:

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.