hive-mind_leave
Remove an agent from the hive-mind Use when native Task is wrong because you need queen-led collective intelligence — Byzantine-FT consensus, broadcast across many worker agents, shared memory with bounded conflict. For a single subagent, native Task is fine. Pair with swarm_init first to set top...
This record as markdown: /tools/io-github-ruvnet-claude-flow/hive-mind-leave.md
What hive-mind_leave does on Claude Flow
AI agents use hive-mind_leave to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
Why hive-mind_leave is rated Medium
Removing an agent from the hive-mind alters the swarm topology and membership, which is a reversible configuration change (the agent is not destroyed, just disassociated). This falls under Write rather than Destructive since it does not irreversibly delete the agent itself. However, misuse could disrupt Byzantine-fault-tolerant consensus or degrade collective intelligence, giving it medium severity.
From the tool's definition 'Remove an agent from the hive-mind' — this modifies the composition of the swarm/collective by detaching an agent from it.
Attacks that exploit this kind of access
The rule that runs hive-mind_leave safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hive-mind_leave, this is the rule to start with:
hive-mind_leave stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every hive-mind_leave call is checked against it from then on.
Questions about hive-mind_leave
Remove an agent from the hive-mind Use when native Task is wrong because you need queen-led collective intelligence — Byzantine-FT consensus, broadcast across many worker agents, shared memory with bounded conflict. For a single subagent, native Task is fine. Pair with swarm_init first to set topology. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hive-mind_leave: 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.
hive-mind_leave is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hive-mind_leave 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 hive-mind_leave. 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.
hive-mind_leave 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.
This server
Across the catalogue