workflow_list
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.
This record as markdown: /tools/hamza-agent-hub-252/workflow-list.md
What workflow_list does on Hamza Agent Hub 252
AI agents call workflow_list to retrieve information from Hamza Agent Hub 252 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why workflow_list is rated Low
This tool retrieves and displays existing workflow information without modifying, deleting, or executing anything. It is a query/list operation with no side effects, fitting squarely in the Read category. The low severity reflects that listing workflows poses minimal risk - it only exposes metadata about existing workflows without the ability to alter them or trigger their execution.
From the tool's definition Tool name is 'workflow_list' and description explicitly states 'List all workflows' - a retrieval operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs workflow_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every workflow_list call is checked against it from then on.
Questions about workflow_list
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 Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.
Register the Hamza Agent Hub 252 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 Hamza Agent Hub 252. Nothing to install.
workflow_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
workflow_list is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hamza Agent Hub 252, and thousands of servers like it.
This server
Across the catalogue