hooks_worker-list
List all 12 background workers with status and capabilities Use when native Bash hooks (via Claude Code\
This record as markdown: /tools/hamza-agent-hub-252/hooks-worker-list.md
What hooks_worker-list does on Hamza Agent Hub 252
AI agents call hooks_worker-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 hooks_worker-list is rated Low
This tool retrieves information about background workers (their status and capabilities) without modifying, executing, or deleting them. It is a read-only enumeration operation. The blast radius is low—an AI agent querying this list cannot cause harm beyond information disclosure of internal system state.
From the tool's definition Tool name 'hooks_worker-list' and description 'List all 12 background workers with status and capabilities' indicate a query/listing operation with no modification or execution of workers.
Attacks that exploit this kind of access
The rule that runs hooks_worker-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 hooks_worker-list, this is the rule to start with:
hooks_worker-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 hooks_worker-list call is checked against it from then on.
Questions about hooks_worker-list
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 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 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 Hamza Agent Hub 252. 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 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