New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

hooks_task-completed

Agent Teams hook — fired when a task is marked complete. Records the completion and, when

SERVERClaude Flow SOURCEclaude-flow
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about hooks_task-completed

What does the hooks_task-completed tool do? +

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.

How do I enforce a policy on hooks_task-completed? +

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.

What risk level is hooks_task-completed? +

hooks_task-completed is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hooks_task-completed? +

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.

How do I block hooks_task-completed completely? +

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.

What MCP server provides hooks_task-completed? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Flow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.