AI agents call forget_relationship to permanently remove resources in Mcp Graph Engine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on graph data by removing edges (relationships). While the blast radius is limited to a single relationship rather than an entire graph, the destructive nature and inability to undo the operation without external recovery mechanisms places it in the Destructive category.
From the tool's definition Tool name 'forget_relationship' combined with description 'Remove an edge from the graph' indicates irreversible deletion of data. The word 'Remove' in the context of graph edges means data is being deleted and cannot be recovered without reconstruction.
Documented attack patterns abuse exactly the kind of access forget_relationship gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Graph Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for forget_relationship:
{
"version": "1",
"default": "deny",
"hide": [
"forget_relationship"
]
} forget_relationship disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove an edge from the graph. It is categorised as a Destructive tool in the Mcp Graph Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Graph Engine MCP server in PolicyLayer and add a rule for forget_relationship: 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 Mcp Graph Engine. Nothing to install.
forget_relationship 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 forget_relationship 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 forget_relationship. 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.
forget_relationship is provided by the Mcp Graph Engine MCP server (utilitydelta/mcp-graph-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Graph Engine, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Mcp Graph Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.