// MCP TOOL REFERENCE

delete_entities

ServerKnowledgeGraph MCP Server
CategoryDestructive

WHAT IT DOES

What delete_entities does on KnowledgeGraph MCP Server

AI agents call delete_entities to permanently remove resources in KnowledgeGraph MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why delete_entities needs a policy

The tool irreversibly deletes data (entities and their relationships) with cascading effects that cannot be undone. The description explicitly states 'irreversible' and 'cascades', confirming this is a destructive operation that qualifies as the most severe category per the classification rules.

From the tool's definition Permanently DELETE entities and all their RELATIONSHIPS. This action is irreversible and cascades to remove all connections.

Documented attack patterns abuse exactly the kind of access delete_entities gives an agent:

POLICY

How to control delete_entities

PolicyLayer is an MCP gateway — it sits between your AI agents and KnowledgeGraph MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entities:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_entities"
  ]
}

delete_entities disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register KnowledgeGraph MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More KnowledgeGraph MCP Server tools

Destructive delete_observations DELETE specific OBSERVATIONS from entities while preserving the entity, its relationships, Destructive delete_relations DELETE specific RELATIONSHIPS between entities while preserving both entities. Use for upd Write remove_tags REMOVE specific TAGS from existing entities to maintain accurate categorization. Use for s Write add_observations ADD new factual observations to existing entities. Requires exact entity names that exist Write add_tags ADD categorical TAGS to existing entities for filtering and organization. Tags are case-se Write create_entities CREATE new entities with OBSERVATIONS and optional tags. MANDATORY: If creating multiple e Write create_relations CREATE directional RELATIONSHIPS between existing entities. Both source and target entitie Read read_graph RETRIEVE the complete KNOWLEDGE GRAPH with all entities and relationships for a project. R

All 11 KnowledgeGraph MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in KnowledgeGraph MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_entities

What does the delete_entities tool do? +

Permanently DELETE entities and all their RELATIONSHIPS. This action is irreversible and cascades to remove all connections. Verify entity existence with search_knowledge first. Consider delete_observations for partial updates. It is categorised as a Destructive tool in the KnowledgeGraph 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_entities? +

Register the KnowledgeGraph MCP Server MCP server in PolicyLayer and add a rule for delete_entities: 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 KnowledgeGraph MCP Server. Nothing to install.

What risk level is delete_entities? +

delete_entities 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_entities? +

Yes. Add a rate_limit block to the delete_entities 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_entities completely? +

Set action: deny in the PolicyLayer policy for delete_entities. 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_entities? +

delete_entities is provided by the KnowledgeGraph MCP Server MCP server (n-r-w/knowledgegraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every KnowledgeGraph MCP Server tool call.

Start from KnowledgeGraph MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

11 KnowledgeGraph MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.