delete_entity

Remove an entity and all its relationships from the knowledge graph

Server Lightrag lightrag-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_entity does on Lightrag

AI agents call delete_entity to permanently remove resources in Lightrag — 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 performs irreversible deletion of entities and cascading relationship removal from a knowledge graph. This is a destructive operation with potential for data loss if misused by an AI agent. The blast radius extends beyond the single entity to dependent relationships, elevating severity to 'high'. Confidence is high due to explicit 'Remove' and 'delete' language in both name and description.

From the tool's definition Tool name 'delete_entity' combined with description 'Remove an entity and all its relationships from the knowledge graph' indicates irreversible deletion. The operation cannot be undone and affects related data (relationships) as well.

Questions about delete_entity

What does the delete_entity tool do? +

Remove an entity and all its relationships from the knowledge graph. It is categorised as a Destructive tool in the Lightrag 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 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. 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 (lightrag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.