cancel_workflow_run
Cancel a running workflow. All pending/running steps are cancelled.
This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/cancel-workflow-run.md
What cancel_workflow_run does on Todo for AI MCP Server
AI agents call cancel_workflow_run to permanently remove resources in Todo for AI MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_workflow_run is rated Critical
An AI agent that decides to call cancel_workflow_run doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Todo for AI MCP Server is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs cancel_workflow_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todo for AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_workflow_run, this is the rule to start with:
cancel_workflow_run is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Todo for AI MCP Server, apply this rule, and every cancel_workflow_run call is checked against it from then on.
Questions about cancel_workflow_run
Cancel a running workflow. All pending/running steps are cancelled. It is categorised as a Destructive tool in the Todo for AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for cancel_workflow_run: 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 Todo for AI MCP Server. Nothing to install.
cancel_workflow_run is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_workflow_run 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 cancel_workflow_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.
cancel_workflow_run is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todo for AI MCP Server, and thousands of servers like it.
Across the catalogue