retry_background_task
Retry a terminal background task as a new traceable task linked to the original.
This record as markdown: /tools/cutpilot/retry-background-task.md
What retry_background_task does on Cutpilot
AI agents invoke retry_background_task to trigger actions in Cutpilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why retry_background_task is rated High
This tool re-executes a previously terminated background task, triggering an external operation. It falls under Execute since it runs/re-runs processing tasks. The blast radius is medium — misuse could cause repeated or unintended video processing operations, but it's not inherently destructive or financial.
From the tool's definition "Retry a terminal background task as a new traceable task linked to the original"
Attacks that exploit this kind of access
The rule that runs retry_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 retry_background_task, this is the rule to start with:
retry_background_task stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cutpilot, apply this rule, and every retry_background_task call is checked against it from then on.
Questions about retry_background_task
Retry a terminal background task as a new traceable task linked to the original. It is categorised as a Execute tool in the Cutpilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cutpilot MCP server in PolicyLayer and add a rule for retry_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.
retry_background_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the retry_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.
Set action: deny in the PolicyLayer policy for retry_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.
retry_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.
More on Cutpilot, and thousands of servers like it.
Across the catalogue