task_results

Retrieve results from completed tasks (V2 compatible). Deprecated: Use tasks/results instead.

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-results.md

WHAT IT DOES

What task_results does on Claude Flow

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

This is a data retrieval operation (retrieve results) from already completed tasks. It performs no modifications, deletions, code execution, or financial transactions. The 'Retrieve' verb and focus on read access to historical task data places this squarely in the Read category.

From the tool's definition Tool name 'task_results' and description 'Retrieve results from completed tasks' indicate a read-only operation that queries data about task outcomes without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

task_results Allowed

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

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

FAQ

Questions about task_results

What does the task_results tool do? +

Retrieve results from completed tasks (V2 compatible). Deprecated: Use tasks/results instead. 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_results? +

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

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

Can I rate-limit task_results? +

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

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

task_results 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 →get_event_results on CTFtime MCP Server → The MCP Attack Database →

Guides

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