agentdb_causal-edge-delete
Delete a causal edge between two memory entries. Returns controller=
This record as markdown: /tools/ruflo/agentdb-causal-edge-delete.md
What agentdb_causal-edge-delete does on Ruflo
AI agents call agentdb_causal-edge-delete to permanently remove resources in Ruflo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why agentdb_causal-edge-delete is rated Critical
This tool permanently removes causal relationships in the agent memory system, which cannot be undone. Deletion of structural metadata (causal edges) that govern agent reasoning chains represents irreversible data destruction. While not as critical as deleting entire memory entries, it is more severe than Write operations.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a causal edge between two memory entries.' The word 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs agentdb_causal-edge-delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agentdb_causal-edge-delete, this is the rule to start with:
agentdb_causal-edge-delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every agentdb_causal-edge-delete call is checked against it from then on.
Questions about agentdb_causal-edge-delete
Delete a causal edge between two memory entries. Returns controller=. It is categorised as a Destructive tool in the Ruflo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ruflo MCP server in PolicyLayer and add a rule for agentdb_causal-edge-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 Ruflo. Nothing to install.
agentdb_causal-edge-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 agentdb_causal-edge-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 agentdb_causal-edge-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.
agentdb_causal-edge-delete is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
Across the catalogue