progress_check

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/progress-check.md

WHAT IT DOES

What progress_check does on Claude Flow

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

This tool queries progress data and returns metrics for monitoring purposes. It performs no writes, deletions, code execution, or financial operations. The mention of "witness/audit trail" refers to how the data is tracked, not capabilities of this tool. The appropriate category is Read, with low severity since progress queries pose minimal risk if misused by an AI agent.

From the tool's definition Tool description states "Get current V3 implementation progress percentage and metrics" — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

progress_check Allowed

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

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

FAQ

Questions about progress_check

What does the progress_check tool do? +

Get current V3 implementation progress percentage and metrics Use when native TodoWrite is wrong because you need cross-session goal-completion tracking with witness/audit trail. For in-session checklists, native TodoWrite is simpler. 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 progress_check? +

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

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

Can I rate-limit progress_check? +

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

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

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