hooks_worker-cancel

Cancel a running worker Use when native Bash hooks (via Claude Code\

SERVERRuflo SOURCEruvnet/ruflo

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ruflo/hooks-worker-cancel.md

WHAT IT DOES

What hooks_worker-cancel does on Ruflo

AI agents call hooks_worker-cancel to permanently remove resources in Ruflo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why hooks_worker-cancel is rated Critical

Cancelling a running worker is an irreversible action — it terminates an in-progress execution, potentially losing work, state, or intermediate results that cannot be recovered. This is analogous to killing a process, which cannot be undone. The blast radius is high because it can disrupt autonomous agent workflows in a multi-agent swarm environment.

From the tool's definition Cancel a running worker

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hooks_worker-cancel safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_worker-cancel, this is the rule to start with:

hooks_worker-cancel Hidden

hooks_worker-cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "hooks_worker-cancel"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every hooks_worker-cancel call is checked against it from then on.

FAQ

Questions about hooks_worker-cancel

What does the hooks_worker-cancel tool do? +

Cancel a running worker Use when native Bash hooks (via Claude Code\. It is categorised as a Destructive tool in the Ruflo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on hooks_worker-cancel? +

Register the Ruflo MCP server in PolicyLayer and add a rule for hooks_worker-cancel: 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_worker-cancel? +

hooks_worker-cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hooks_worker-cancel? +

Yes. Add a rate_limit block to the hooks_worker-cancel 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_worker-cancel completely? +

Set action: deny in the PolicyLayer policy for hooks_worker-cancel. 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_worker-cancel? +

hooks_worker-cancel 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.

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →