swarm_status

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-status.md

WHAT IT DOES

What swarm_status does on Claude Flow

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

This tool retrieves the current state of a swarm system (topology, consensus mechanism, shared memory, anti-drift gates) for informational purposes. No modifications, deletions, code execution, or financial operations are performed. It is purely observational/query functionality, making it a Read category tool with low severity risk.

From the tool's definition 'Get swarm status' - retrieves status information from persistent state without modifying or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

swarm_status Allowed

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

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

FAQ

Questions about swarm_status

What does the swarm_status tool do? +

Get swarm status from persistent state 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_status? +

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

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

Can I rate-limit swarm_status? +

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

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

swarm_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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