Remove entities and edges that have decayed below threshold. DESTRUCTIVE — always preview first. Requires user confirmation before execute mode.
AI agents call graph_prune 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 permanently deletes entities and edges from the user's personal knowledge graph based on decay thresholds. Even with preview and confirmation requirements as mitigations, the action itself cannot be undone—deleted nodes and relationships are lost. This fits the Destructive category (irreversibly deletes data) rather than Write (which is reversible).
From the tool's definition Tool description explicitly labels as 'DESTRUCTIVE' and states it 'Remove[s] entities and edges' from the knowledge graph. These are irreversible deletions of data.
Attacks that exploit this kind of access
Remove entities and edges that have decayed below threshold. DESTRUCTIVE — always preview first. Requires user confirmation before execute mode. 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_prune: 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_prune 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_prune 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_prune. 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_prune 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 →