swarm_health

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/swarm-health.md

WHAT IT DOES

What swarm_health does on Claude Flow

AI agents call swarm_health 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 swarm_health is rated Low

This tool retrieves and queries the current state of multi-agent swarms (topology, consensus mechanisms, shared memory, drift detection). It performs inspection only and explicitly contrasts itself with Task tools used for actual execution, making it a read-only monitoring/diagnostic function. No data is created, modified, deleted, or executed.

From the tool's definition Tool name 'swarm_health' and description explicitly states 'Check swarm health status' and 'real state inspection' — purely observational operations with no side effects. It inspects topology, consensus, and shared memory state without modifying them.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

swarm_health Allowed

swarm_health 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": {
    "swarm_health": {}
  }
}

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 swarm_health call is checked against it from then on.

FAQ

Questions about swarm_health

What does the swarm_health tool do? +

Check swarm health status with real state inspection Use when native Task tool is wrong because you need multi-agent coordination — topology (hierarchical/mesh/star), consensus (raft/byzantine/gossip/crdt/quorum), shared memory namespace, or anti-drift gates. For independent one-shot subagents, native Task is fine; spawn each separately. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on swarm_health? +

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

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

Can I rate-limit swarm_health? +

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

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

swarm_health 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 →