Delete entity relationship (removes knowledge graph edge). WHEN: Removing obsolete or incorrect relationships. Use carefully - this is permanent. BEHAVIOR: Removes relationship between entities. Entities remain intact. Cannot be undone. Args: relationship_id: Relationship ID to delete ctx: Contex...
AI agents call delete_entity_relationship to permanently remove resources in Forgetful — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes relationship records from the knowledge base without reversibility. While it does not delete the entities themselves (only the edge/relationship), the permanent nature of the deletion and inability to undo the operation places it in the Destructive category rather than Write.
From the tool's definition Tool description states 'removes knowledge graph edge', 'This is permanent', and 'Cannot be undone.' The tool irreversibly deletes data from the knowledge graph.
Documented attack patterns abuse exactly the kind of access delete_entity_relationship gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entity_relationship:
{
"version": "1",
"default": "deny",
"hide": [
"delete_entity_relationship"
]
}delete_entity_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.
Delete entity relationship (removes knowledge graph edge). WHEN: Removing obsolete or incorrect relationships. Use carefully - this is permanent. BEHAVIOR: Removes relationship between entities. Entities remain intact. Cannot be undone. Args: relationship_id: Relationship ID to delete ctx: Context (automatically injected) Returns: Success confirmation with deleted relationship ID Raises: ToolError: If deletion fails. It is categorised as a Destructive tool in the Forgetful MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Forgetful MCP server in PolicyLayer and add a rule for delete_entity_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 Forgetful. Nothing to install.
delete_entity_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 delete_entity_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 delete_entity_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.
delete_entity_relationship is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.