Delete a hierarchical-memory entry by key. Returns controller=
AI agents call agentdb_hierarchical-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.
The tool performs deletion (remove/purge) of data entries from a hierarchical memory system. Deletion is irreversible and cannot be undone, placing it in the Destructive category rather than Write.
From the tool's definition Tool name includes 'delete' and description states 'Delete a hierarchical-memory entry by key'. This is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a hierarchical-memory entry by key. 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_hierarchical-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_hierarchical-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_hierarchical-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_hierarchical-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_hierarchical-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.
agentdb_hierarchical-delete is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →