hooks_worker-status

Get status of a specific worker or all active workers Use when native Bash hooks (via Claude Code\

SERVERRuflo SOURCEruvnet/ruflo

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/ruflo/hooks-worker-status.md

WHAT IT DOES

What hooks_worker-status does on Ruflo

AI agents call hooks_worker-status to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why hooks_worker-status is rated Low

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

RECOMMENDED RULE

The rule that runs hooks_worker-status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_worker-status, this is the rule to start with:

hooks_worker-status Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every hooks_worker-status call is checked against it from then on.

FAQ

Questions about hooks_worker-status

What does the hooks_worker-status tool do? +

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.

How do I enforce a policy on hooks_worker-status? +

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.

What risk level is hooks_worker-status? +

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

Can I rate-limit hooks_worker-status? +

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.

How do I block hooks_worker-status completely? +

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.

What MCP server provides hooks_worker-status? +

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.

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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