federation_wg_attest · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What federation_wg_attest does on Claude Flow

AI agents use federation_wg_attest to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.

WHY IT NEEDS A POLICY

Why federation_wg_attest needs a policy

The tool writes a signed attestation entry to a log file. It creates/appends data (the witness entry) to a persistent log, which is a Write operation. While it involves signing and federation coordination, the core action is appending a log record. It's not destructive (idempotent, append-only), not financial, and not executing code.

From the tool's definition emit an operator-signed attestation entry for a coordination change... operator appends it to .claude-flow/federation/wg-changes.log. Idempotent — re-attesting the same change just appends another entry

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

federation_wg_attest Rate-limited

federation_wg_attest stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "federation_wg_attest": {
      "limits": [
        {
          "counter": "federation_wg_attest_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 federation_wg_attest

What does the federation_wg_attest tool do? +

ADR-111 Phase 6 (witness chain): emit an operator-signed attestation entry for a coordination change. Returns the canonical bytes the operator signs + the witness entry; operator appends it to .claude-flow/federation/wg-changes.log. Idempotent — re-attesting the same change just appends another entry. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on federation_wg_attest? +

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

federation_wg_attest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit federation_wg_attest? +

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

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

federation_wg_attest 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.