Permanently delete an entity node and all its edges by ID. Use for removing duplicate or erroneous nodes. Cannot be undone.
AI agents call graph_delete to permanently remove resources in Graph-Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data from the knowledge graph. While the scope is limited to a single entity and its edges (not the entire graph), the permanent and unrecoverable nature of deletion, combined with the potential for an AI agent to mistakenly delete important nodes due to misidentified IDs or context confusion, constitutes a high-severity destructive action.
From the tool's definition Tool description explicitly states: "Permanently delete an entity node and all its edges by ID" and "Cannot be undone." The verb "delete" combined with "permanently" and "cannot be undone" are definitive markers of destructive operations.
Attacks that exploit this kind of access
Permanently delete an entity node and all its edges by ID. Use for removing duplicate or erroneous nodes. Cannot be undone. It is categorised as a Destructive tool in the Graph-Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Graph-Memory MCP server in PolicyLayer and add a rule for graph_delete: 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 Graph-Memory. Nothing to install.
graph_delete 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 graph_delete 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 graph_delete. 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.
graph_delete is provided by the Graph-Memory MCP server (stevepridemore/graph-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →