Delete edges from the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools, and the operation cannot be undone. Use cases: 1. Delete incorrectly created relationships 2. Update relationship structure between nodes 3. Clean up redundant relationships w...
Part of the Knowledge Graph Server server.
Free to start. No card required.
AI agents may call delete_edge 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. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call delete_edge in a loop, permanently destroying resources in Knowledge Graph Server. There is no undo for destructive operations. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"hide": [
"delete_edge"
]
}See the full Knowledge Graph Server policy for all 15 tools.
These attack patterns abuse exactly the kind of access delete_edge gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Delete edges from the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools, and the operation cannot be undone. Use cases: 1. Delete incorrectly created relationships 2. Update relationship structure between nodes 3. Clean up redundant relationships when restructuring the graph Usage recommendations: 1. First call list_graphs to get target graph information 2. Use get_node_details to get edge details 3. Confirm deletion won't break important relationship structures 4. Set confirmDelete to true to confirm deletion Important notes: - Deleting edges won't affect related nodes - Need to call get_node_details again to view updated relationships Return data: - data: Deletion result * id: Deleted edge ID * 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.
Register the Knowledge Graph Server MCP server in PolicyLayer and add a rule for delete_edge: 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 Knowledge Graph Server. Nothing to install.
delete_edge 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_edge 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.
Set action: deny in the PolicyLayer policy for delete_edge. 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_edge is provided by the Knowledge Graph Server MCP server (aiuluna/knowledge-graph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Knowledge Graph Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.