hooks_post-task
Record task completion for learning Use when native Bash hooks (via Claude Code\
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.
Attacks that exploit this kind of access
The rule that runs hooks_post-task 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_post-task, this is the rule to start with:
hooks_post-task 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_post-task call is checked against it from then on.
Questions about hooks_post-task
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.
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.
hooks_post-task 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_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.
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.
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.
This server
Across the catalogue