hooks_teammate-idle
Agent Teams hook — fired when a teammate agent finishes its turn; reports whether a pending task can be auto-assigned. Use when native Task is wrong because you have a persistent multi-agent team with a shared task list and want idle workers picked up automatically rather than re-spawning subagen...
This record as markdown: /tools/io-github-ruvnet-claude-flow/hooks-teammate-idle.md
What hooks_teammate-idle does on Claude Flow
AI agents invoke hooks_teammate-idle to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why hooks_teammate-idle is rated High
This tool triggers an orchestration hook that fires events and drives auto-assignment of tasks to idle agents — it causes external operations (task dispatching, agent coordination) whose effects depend on the state of the multi-agent system. It is not a simple read (it acknowledges events and triggers downstream logic), nor purely write (it orchestrates agent behavior).
From the tool's definition 'fired when a teammate agent finishes its turn; reports whether a pending task can be auto-assigned' and 'Auto-assignment is delegated to the task-queue consumer — this acknowledges the event today'
Attacks that exploit this kind of access
The rule that runs hooks_teammate-idle 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_teammate-idle, this is the rule to start with:
hooks_teammate-idle stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every hooks_teammate-idle call is checked against it from then on.
Questions about hooks_teammate-idle
Agent Teams hook — fired when a teammate agent finishes its turn; reports whether a pending task can be auto-assigned. Use when native Task is wrong because you have a persistent multi-agent team with a shared task list and want idle workers picked up automatically rather than re-spawning subagents. For a one-shot Task, native Task is fine. (Auto-assignment is delegated to the task-queue consumer — this acknowledges the event today.). It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_teammate-idle: 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_teammate-idle is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hooks_teammate-idle 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_teammate-idle. 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_teammate-idle 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.
More on Claude Flow, and thousands of servers like it.
Across the catalogue