Delete nodes from the knowledge graph. This tool must be used in conjunction with list_graphs tool, and the operation cannot be undone. Use cases: 1. Delete incorrectly created nodes 2. Delete nodes that are no longer needed 3. Delete redundant nodes when restructuring the graph Usage recommenda...
Part of the Knowledge Graph Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call delete_node to permanently remove or destroy resources in Knowledge Graph Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call delete_node in a loop, permanently destroying resources in Knowledge Graph Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
delete_node:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Knowledge Graph Server policy for all 15 tools.
Agents calling destructive-class tools like delete_node have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
delete_node is one of the critical-risk operations in Knowledge Graph Server. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Delete nodes from the knowledge graph. This tool must be used in conjunction with list_graphs tool, and the operation cannot be undone. Use cases: 1. Delete incorrectly created nodes 2. Delete nodes that are no longer needed 3. Delete redundant nodes when restructuring the graph Usage recommendations: 1. First call list_graphs to get target graph and node information 2. Use get_node_details to check node's associated resources and relationships 3. Confirm deletion won't affect other important nodes 4. Set confirmDelete to true to confirm deletion 5. Recommended to backup important data before deletion Important notes: - Deleting a node will also delete all edges related to that node - If the node has associated resources, they won't be deleted but will be unlinked Return data: - data: Deletion result * id: Deleted node ID * name: Node name * type: Node type * deletedAt: Deletion time. It is categorised as a Destructive tool in the Knowledge Graph Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for delete_node. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Knowledge Graph Server MCP server.
delete_node 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_node rule in your Intercept 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 Intercept policy for delete_node. 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_node is provided by the Knowledge Graph Server MCP server (aiuluna/knowledge-graph-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept