task_status

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/task-status.md

WHAT IT DOES

What task_status does on Claude Flow

AI agents call task_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.

RISK

Why task_status is rated Low

This tool queries task metadata and state from a database. While it accesses an enterprise swarm system, the function is purely informational retrieval with no side effects. The guidance that TodoWrite is "simpler and faster" for in-session use confirms this is a data-retrieval tool, not a write or execute tool. Risk is low because querying task status cannot alter system state or trigger unwanted actions.

From the tool's definition Tool name is "task_status" and description states "Get task status"; it retrieves task information from persistent storage (.swarm/memory.db) without modifying, deleting, or executing external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

task_status Allowed

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

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

FAQ

Questions about task_status

What does the task_status tool do? +

Get task status Use when native TodoWrite is wrong because you need cross-session task persistence, agent assignment, dependency tracking, or completion analytics in the .swarm/memory.db. For in-session checklists native TodoWrite is simpler and faster. 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 task_status? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for task_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.

What risk level is task_status? +

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

Can I rate-limit task_status? +

Yes. Add a rate_limit block to the task_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.

How do I block task_status completely? +

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

What MCP server provides task_status? +

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

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →