hive-mind_consensus · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What hive-mind_consensus does on Claude Flow

AI agents invoke hive-mind_consensus to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why hive-mind_consensus needs a policy

This tool triggers distributed consensus operations across multiple agents using BFT/Raft/Quorum protocols. It orchestrates external agent coordination and communication — broadcasting to worker agents and managing shared memory state. This is an Execute-category action because it runs multi-agent coordination logic with side effects dependent on arguments (topology, strategy, proposals).

From the tool's definition Propose or vote on consensus with BFT, Raft, or Quorum strategies... broadcast across many worker agents, shared memory with bounded conflict

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hive-mind_consensus Rate-limited

hive-mind_consensus stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hive-mind_consensus": {
      "limits": [
        {
          "counter": "hive-mind_consensus_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Flow, so you can run agents against it safely.

FAQ

Questions about hive-mind_consensus

What does the hive-mind_consensus tool do? +

Propose or vote on consensus with BFT, Raft, or Quorum strategies 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 Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hive-mind_consensus? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hive-mind_consensus: 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 hive-mind_consensus? +

hive-mind_consensus is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hive-mind_consensus? +

Yes. Add a rate_limit block to the hive-mind_consensus 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 hive-mind_consensus completely? +

Set action: deny in the PolicyLayer policy for hive-mind_consensus. 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 hive-mind_consensus? +

hive-mind_consensus 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.