coordination_metrics

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/coordination-metrics.md

WHAT IT DOES

What coordination_metrics does on Claude Flow

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

This tool retrieves telemetry/monitoring data about agent coordination (voting, sync, load-balancing consensus). It is purely informational—an agent querying it observes system state without triggering side effects. The description explicitly contrasts it with task dispatch/orchestration (which would be Execute or Write), positioning it as a diagnostic/observability tool.

From the tool's definition Tool name includes 'metrics' and description states 'Get coordination metrics' — a retrieval operation. No data modification, deletion, execution of external code, or financial transaction occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

coordination_metrics Allowed

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

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

FAQ

Questions about coordination_metrics

What does the coordination_metrics tool do? +

Get coordination metrics 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 Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on coordination_metrics? +

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

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

Can I rate-limit coordination_metrics? +

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

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

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