hooks_task-completed · Ruflo MCP: Risk & Policy

WHAT IT DOES

What hooks_task-completed does on Ruflo

AI agents use hooks_task-completed 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_task-completed needs a policy

The tool fires when a task is marked complete and records the completion event, which is a write/state-modification action. The description is truncated, so full behavior is unclear, but the core action appears to be recording/updating task state. No indication of destructive, financial, or execution behavior from the available text.

From the tool's definition 'fired when a task is marked complete. Records the completion' — this hook triggers a write/record operation upon task completion

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_task-completed Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_task-completed": {
      "limits": [
        {
          "counter": "hooks_task-completed_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_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 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_task-completed? +

Register the Ruflo 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 Ruflo. 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 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_task-completed 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 →