List all 12 background workers with status and capabilities Use when native Bash hooks (via Claude Code\
AI agents call hooks_worker-list to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/list operation to enumerate background workers and their metadata. It has no side effects, does not modify state, execute code, delete resources, or commit financial transactions. The blast radius of misuse is minimal—an agent could only gain visibility into worker status, not control or harm them.
From the tool's definition Tool name and description indicate it 'List all 12 background workers with status and capabilities' — a read-only operation that retrieves and displays information without modification or execution.
Attacks that exploit this kind of access
List all 12 background workers with status and capabilities Use when native Bash hooks (via Claude Code\. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_worker-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.
hooks_worker-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 hooks_worker-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 hooks_worker-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.
hooks_worker-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.