Get status of a specific worker or all active workers Use when native Bash hooks (via Claude Code\
AI agents call hooks_worker-status 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 queries the state of workers without triggering actions, modifying data, or executing commands. It is a pure information retrieval operation, fitting the Read category. Severity is low because status queries have no blast radius—they cannot corrupt data, trigger unintended operations, or cause side effects. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'hooks_worker-status' and description 'Get status of a specific worker or all active workers' indicate read-only retrieval of status information with no modification or execution capability.
Attacks that exploit this kind of access
Get status of a specific worker or all active workers 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-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.
hooks_worker-status 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-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.
Set action: deny in the PolicyLayer policy for hooks_worker-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.
hooks_worker-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.