New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

agentdb_hierarchical-delete

Delete a hierarchical-memory entry by key. Returns controller=

SERVERClaude Flow SOURCEclaude-flow
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/agentdb-hierarchical-delete.md

What agentdb_hierarchical-delete does on Claude Flow

AI agents call agentdb_hierarchical-delete to permanently remove resources in Claude Flow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why agentdb_hierarchical-delete is rated Critical

This tool permanently removes data from a hierarchical memory store without possibility of recovery. While the blast radius is constrained to a single memory entry (not system-wide), deletion operations are inherently destructive and cannot be undone.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a hierarchical-memory entry by key'. The action is irreversible data removal.

Questions about agentdb_hierarchical-delete

What does the agentdb_hierarchical-delete tool do? +

Delete a hierarchical-memory entry by key. Returns controller=. It is categorised as a Destructive tool in the Claude Flow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on agentdb_hierarchical-delete? +

Register the Claude Flow 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 Claude Flow. Nothing to install.

What risk level is agentdb_hierarchical-delete? +

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.

Can I rate-limit agentdb_hierarchical-delete? +

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.

How do I block agentdb_hierarchical-delete completely? +

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.

What MCP server provides agentdb_hierarchical-delete? +

agentdb_hierarchical-delete is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Claude Flow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Flow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.