MCP Tool Reference High Risk

cancel_run

Cancel an active run

Part of the Trigger.dev MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

WHEN AI AGENTS USE THIS TOOL

AI agents invoke cancel_run to trigger processes or run actions in Trigger.dev. Execute operations can have side effects beyond the immediate call — triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

WHY ENFORCE A POLICY ON CANCEL_RUN

cancel_run can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

trigger-dev.yaml
tools:
  cancel_run:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Trigger.dev policy for all 14 tools.

DETAILS

Tool Name

cancel_run

Category

Execute

Risk Level

High

MORE TRIGGER.DEV TOOLS

View all 14 tools →

SIMILAR EXECUTE TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the cancel_run tool do?

Cancel an active run. It is categorised as a Execute tool in the Trigger.dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cancel_run?

Add a rule in your Intercept YAML policy under the tools section for cancel_run. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Trigger.dev MCP server.

What risk level is cancel_run?

cancel_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cancel_run?

Yes. Add a rate_limit block to the cancel_run rule in your Intercept 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_run completely?

Set action: deny in the Intercept policy for cancel_run. 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_run?

cancel_run is provided by the Trigger.dev MCP server (triggerdotdev/trigger.dev). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON TRIGGER.DEV

Open source. One binary. Zero dependencies.