cancel_execution

Cancel a running workflow execution. Only works on executions with status

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

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/flowdot-llc-mcp-server/cancel-execution.md

WHAT IT DOES

What cancel_execution does on FlowDot MCP Server

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

RISK

Why cancel_execution is rated Critical

Cancelling a running execution irreversibly terminates it — the in-progress work is lost and cannot be resumed. This is a non-reversible action akin to destruction of an in-flight process, making Destructive the most appropriate category. Severity is high because aborting workflows can have significant downstream consequences (data loss, incomplete processing, broken pipelines).

From the tool's definition cancel_execution: 'Cancel a running workflow execution. Only works on executions with status'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_execution safely

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

cancel_execution Hidden

cancel_execution 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_execution"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about cancel_execution

What does the cancel_execution tool do? +

Cancel a running workflow execution. Only works on executions with status. It is categorised as a Destructive tool in the FlowDot MCP Server 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_execution? +

Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for cancel_execution: 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 FlowDot MCP Server. Nothing to install.

What risk level is cancel_execution? +

cancel_execution 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_execution? +

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

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

cancel_execution is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server 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 →