hooks_task-completed
Agent Teams hook — fired when a task is marked complete. Records the completion and, when
This record as markdown: /tools/io-github-ruvnet-claude-flow/hooks-task-completed.md
What hooks_task-completed does on Claude Flow
AI agents use hooks_task-completed to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
Why hooks_task-completed is rated Medium
The tool is a lifecycle hook that fires on task completion and records that completion, which is a write operation (creating/updating a record). It does not appear to execute arbitrary code, delete data, or involve financial operations. Confidence is moderate because the description is truncated and full behavior is unclear.
From the tool's definition 'fired when a task is marked complete. Records the completion' — implies writing a completion record/event
Attacks that exploit this kind of access
The rule that runs hooks_task-completed 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_task-completed, this is the rule to start with:
hooks_task-completed stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_task-completed call is checked against it from then on.
Questions about hooks_task-completed
Agent Teams hook — fired when a task is marked complete. Records the completion and, when. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_task-completed: 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_task-completed is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hooks_task-completed 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_task-completed. 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_task-completed 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.
This server
Across the catalogue