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

hooks_post-task

Record task completion for learning Use when native Bash hooks (via Claude Code\

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-post-task.md

What hooks_post-task does on Claude Flow

AI agents use hooks_post-task 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_post-task is rated Medium

This tool creates or modifies records (task completion logs) rather than merely reading data, placing it in the Write category. Severity is medium because misuse could pollute learning datasets or task histories, affecting downstream orchestration decisions, but the blast radius is limited compared to destructive operations.

From the tool's definition Tool name includes 'post-task' and description states 'Record task completion', indicating it writes or logs data about task events. The phrase 'for learning' suggests it stores this data for future use.

Questions about hooks_post-task

What does the hooks_post-task tool do? +

Record task completion for learning Use when native Bash hooks (via Claude Code\. 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_post-task? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_post-task: 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_post-task? +

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

Can I rate-limit hooks_post-task? +

Yes. Add a rate_limit block to the hooks_post-task 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_post-task completely? +

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

hooks_post-task 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.