AI agents call hooks_worker-status to retrieve information from Ruflo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about workers without modifying, executing, or destructively altering any state. It is a simple monitoring/query function. The low severity reflects that reading worker status information poses minimal risk even if misused by an agent, as it cannot directly impact system operations or data integrity.
From the tool's definition Tool name 'hooks_worker-status' and description 'Get status of a specific worker or all active workers' indicate a query/retrieval operation with no side effects. The verb 'Get' and reference to 'status' retrieval confirm this is a read-only operation.
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 Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
hooks_worker-status is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →