federation_wg_status
ADR-111 Phase 6: WG mesh state — per-peer trust level, mesh IP, suspended/evicted flags, and the AllowedIPs slice each peer currently has. Use to inspect what the breaker has propagated to the L3 layer.
This record as markdown: /tools/io-github-ruvnet-claude-flow/federation-wg-status.md
What federation_wg_status does on Claude Flow
AI agents call federation_wg_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.
Why federation_wg_status is rated Low
This tool retrieves and displays network mesh status information without side effects. It queries current state of working group peers and their configuration as propagated by a breaker to the L3 layer. No data is created, modified, deleted, or executed. The blast radius of misuse is low—an agent could inspect network configuration it may not be authorized to see, but cannot alter it or trigger actions.
From the tool's definition Tool name and description indicate inspection/querying of mesh state: 'status', 'inspect what the breaker has propagated'. No modification, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
The rule that runs federation_wg_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 federation_wg_status, this is the rule to start with:
federation_wg_status is read-only, so it stays allowed. 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 federation_wg_status call is checked against it from then on.
Questions about federation_wg_status
ADR-111 Phase 6: WG mesh state — per-peer trust level, mesh IP, suspended/evicted flags, and the AllowedIPs slice each peer currently has. Use to inspect what the breaker has propagated to the L3 layer. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for federation_wg_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.
federation_wg_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the federation_wg_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.
Set action: deny in the PolicyLayer policy for federation_wg_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.
federation_wg_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.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue