AI agents call cancel_workflow_run to permanently remove resources in GitHub Actions MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling a workflow run is an irreversible action — a canceled run cannot be un-canceled and any in-progress work is lost. The server description explicitly lists 'canceling' as a managed operation. While the tool description is empty (reducing confidence slightly), the name clearly indicates cancellation, which is a non-recoverable termination of a running process.
From the tool's definition Tool name 'cancel_workflow_run' and server description mentions 'canceling' workflows as a capability
Documented attack patterns abuse exactly the kind of access cancel_workflow_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Actions MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_workflow_run:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_workflow_run"
]
}cancel_workflow_run disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
cancel_workflow_run. It is categorised as a Destructive tool in the GitHub Actions MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub Actions 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 GitHub Actions 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 GitHub Actions MCP Server MCP server (ko1ynnky/github-actions-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitHub Actions MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 GitHub Actions MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.