workflow_list

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/workflow-list.md

WHAT IT DOES

What workflow_list does on Claude Flow

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

This tool retrieves and displays workflow metadata without modifying, creating, deleting, or executing anything. It is purely informational. The moderate complexity of the workflow system it introspects does not elevate the risk of a read-only listing operation. Severity is low because misuse (e.g., an agent listing all workflows) causes no direct harm—it may leak workflow names or structure, but no action is taken.

From the tool's definition Tool name 'workflow_list' and description explicitly states 'List all workflows' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

workflow_list Allowed

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

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

FAQ

Questions about workflow_list

What does the workflow_list tool do? +

List all workflows Use when native TodoWrite + sequential Bash is wrong because the work has a real dependency graph that needs persistence, retry policy, pause/resume, and step-output binding across LLM-driven steps. For a single linear todo list, native TodoWrite 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 workflow_list? +

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

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

Can I rate-limit workflow_list? +

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

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

workflow_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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