delete_entity

Delete an entity from the knowledge graph

Server LightRAG MCP Server lalitsuryan/lightragmcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_entity does on LightRAG MCP Server

AI agents call delete_entity to permanently remove resources in 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 needs a policy

This tool irreversibly removes entities from a knowledge graph. Unlike Write operations that create or update data, deletion cannot be undone without external intervention (e.g., backups or redo logs). The high severity reflects that an AI agent could corrupt the knowledge base by deleting critical entities. High confidence due to explicit 'delete' terminology and destructive intent.

From the tool's definition delete_entity: Delete an entity from the knowledge graph — performs deletion operation on graph data that cannot be reversed; the verb 'delete' combined with modification of persistent knowledge graph state indicates irreversible data removal.

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 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 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 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 LightRAG MCP Server MCP server (lalitsuryan/lightragmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

delete_entity is one line of LightRAG MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.