github_cancel_workflow_run

Cancel a running workflow.

SERVERGithub SOURCEdkeeno/github-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-cancel-workflow-run.md

WHAT IT DOES

What github_cancel_workflow_run does on Github

AI agents invoke github_cancel_workflow_run to trigger actions in Github. 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.

RISK

Why github_cancel_workflow_run is rated High

Cancelling a workflow run is an external operation that interrupts an active CI/CD process. It is not merely reading data, nor does it delete/overwrite data irreversibly, but it triggers an operational change (stopping a workflow) with potentially significant consequences if an agent misuses it — e.g., aborting deployments or critical automation pipelines.

From the tool's definition Cancel a running workflow

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_cancel_workflow_run safely

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

github_cancel_workflow_run Rate-limited

github_cancel_workflow_run 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_cancel_workflow_run": {
      "limits": [
        {
          "counter": "github_cancel_workflow_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_cancel_workflow_run

What does the github_cancel_workflow_run tool do? +

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

How do I enforce a policy on github_cancel_workflow_run? +

Register the Github MCP server in PolicyLayer and add a rule for github_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. Nothing to install.

What risk level is github_cancel_workflow_run? +

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

Can I rate-limit github_cancel_workflow_run? +

Yes. Add a rate_limit block to the github_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.

How do I block github_cancel_workflow_run completely? +

Set action: deny in the PolicyLayer policy for github_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.

What MCP server provides github_cancel_workflow_run? +

github_cancel_workflow_run is provided by the Github MCP server (dkeeno/github-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 Github, and thousands of servers like it.

This server

All 69 Github tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →