hooks_worker-detect

Detect worker triggers from user prompt (for UserPromptSubmit hook) Use when native Bash hooks (via Claude Code\

SERVERClaude Flow SOURCEclaude-flow

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/io-github-ruvnet-claude-flow/hooks-worker-detect.md

WHAT IT DOES

What hooks_worker-detect does on Claude Flow

AI agents call hooks_worker-detect to retrieve information from Claude Flow 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-detect is rated Low

The tool appears to detect/identify worker triggers from a prompt input, which is a read/analysis operation. However, its output may be used to spawn or trigger workers (via 'UserPromptSubmit hook'), meaning misuse could indirectly cause higher-severity downstream actions. The description is incomplete (truncated), which reduces confidence.

From the tool's definition 'Detect worker triggers from user prompt' - the tool analyzes/reads a user prompt to identify triggers, suggesting a read/analysis operation with no direct side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hooks_worker-detect safely

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

hooks_worker-detect Allowed

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

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

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

FAQ

Questions about hooks_worker-detect

What does the hooks_worker-detect tool do? +

Detect worker triggers from user prompt (for UserPromptSubmit hook) 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.

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

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_worker-detect: 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.

What risk level is hooks_worker-detect? +

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

Can I rate-limit hooks_worker-detect? +

Yes. Add a rate_limit block to the hooks_worker-detect 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-detect completely? +

Set action: deny in the PolicyLayer policy for hooks_worker-detect. 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-detect? +

hooks_worker-detect 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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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