cancel_background_task

Cancel a queued or running background task while preserving its history.

SERVERCutpilot SOURCEHellotravisss/cutpilot

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/cutpilot/cancel-background-task.md

WHAT IT DOES

What cancel_background_task does on Cutpilot

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

RISK

Why cancel_background_task is rated Critical

An AI agent that decides to call cancel_background_task doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Cutpilot is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_background_task safely

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

cancel_background_task Hidden

cancel_background_task 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": [
    "cancel_background_task"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about cancel_background_task

What does the cancel_background_task tool do? +

Cancel a queued or running background task while preserving its history. It is categorised as a Destructive tool in the Cutpilot 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 cancel_background_task? +

Register the Cutpilot MCP server in PolicyLayer and add a rule for cancel_background_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 Cutpilot. Nothing to install.

What risk level is cancel_background_task? +

cancel_background_task 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 cancel_background_task? +

Yes. Add a rate_limit block to the cancel_background_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 cancel_background_task completely? +

Set action: deny in the PolicyLayer policy for cancel_background_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 cancel_background_task? +

cancel_background_task is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cutpilot, and thousands of servers like it.

This server

All 219 Cutpilot tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →