hive-mind_memory

Access hive shared memory 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.

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/hive-mind-memory.md

WHAT IT DOES

What hive-mind_memory does on Claude Flow

AI agents call hive-mind_memory to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why hive-mind_memory is rated Low

The tool is described as 'Access hive shared memory,' which suggests a read operation. However, 'shared memory with bounded conflict' implies possible write/update semantics as well (e.g., consensus-based updates). The description is ambiguous about whether this tool only reads or also writes to shared memory.

From the tool's definition 'Access hive shared memory' — primary action is accessing/reading shared memory; no explicit write, delete, or execute semantics described

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hive-mind_memory 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_memory, this is the rule to start with:

hive-mind_memory Allowed

hive-mind_memory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hive-mind_memory": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every hive-mind_memory call is checked against it from then on.

FAQ

Questions about hive-mind_memory

What does the hive-mind_memory tool do? +

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

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

hive-mind_memory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hive-mind_memory? +

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

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

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

KEEP EXPLORING

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

This server

All 496 Claude Flow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →