hooks_post-task · Ruflo MCP: Risk & Policy

WHAT IT DOES

What hooks_post-task does on Ruflo

AI agents use hooks_post-task to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.

WHY IT NEEDS A POLICY

Why hooks_post-task needs a policy

This tool creates or modifies learning records (task completion logs) in the agent system's state, which is reversible data modification. It does not delete data (not Destructive), execute arbitrary operations (not Execute), move money (not Financial), or merely read data (not Read).

From the tool's definition Tool name 'hooks_post-task' and description 'Record task completion for learning' indicate the tool writes/logs task completion data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_post-task Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_post-task": {
      "limits": [
        {
          "counter": "hooks_post-task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ruflo, so you can run agents against it safely.

FAQ

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 Ruflo 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 Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

hooks_post-task is one line of Ruflo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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