coordination_sync · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What coordination_sync does on Claude Flow

AI agents invoke coordination_sync to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why coordination_sync needs a policy

This tool orchestrates state synchronization and consensus voting across multiple agents/nodes. It triggers external operations whose effects depend on runtime arguments and involve coordination across distributed components.

From the tool's definition "Synchronize state across nodes" and "crosses multiple agents that need to vote/sync/load-balance" — triggers cross-agent coordination and consensus operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

coordination_sync Rate-limited

coordination_sync stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "coordination_sync": {
      "limits": [
        {
          "counter": "coordination_sync_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 coordination_sync

What does the coordination_sync tool do? +

Synchronize state across nodes Use when native Task is wrong because the work crosses multiple agents that need to vote/sync/load-balance — TodoWrite + a single Task cannot orchestrate consensus. For one-off subtask dispatch, native Task is fine. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on coordination_sync? +

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

coordination_sync is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit coordination_sync? +

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

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

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