cancel_workflow_run · GitHub Repos Manager MCP Server MCP

WHAT IT DOES

What cancel_workflow_run does on GitHub Repos Manager MCP Server

AI agents invoke cancel_workflow_run to trigger actions in GitHub Repos Manager MCP Server. 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.

THE RISK

High Risk

Why cancel_workflow_run needs a policy

Cancelling a workflow run is an external operational action that terminates an in-progress CI/CD process. It doesn't delete data irreversibly, but it does interrupt and stop execution of running automated pipelines, which can have significant downstream effects on deployments, tests, and automated processes.

From the tool's definition Cancel running workflows

Documented attack patterns abuse exactly the kind of access cancel_workflow_run gives an agent:

POLICY

How to control cancel_workflow_run

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Repos Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_workflow_run:

policy.json

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

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.

Create a free account and register GitHub Repos Manager MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitHub Repos Manager MCP Server tools

Destructive delete_deploy_key Remove deploy keys. Destructive delete_file Delete a file from a repository. Destructive delete_issue_comment Delete an issue comment Destructive delete_label Delete a label from a repository Destructive delete_milestone Delete a milestone Destructive delete_webhook Remove webhooks. Execute trigger_workflow Manually trigger workflow dispatches (handle input parameters). Write remove_assignees_from_issue Remove assignees from an issue

All 84 GitHub Repos Manager MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in GitHub Repos Manager MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cancel_workflow_run

What does the cancel_workflow_run tool do? +

Cancel running workflows. It is categorised as a Execute tool in the GitHub Repos Manager MCP Server 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_workflow_run? +

Register the GitHub Repos Manager 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 Repos Manager MCP Server. Nothing to install.

What risk level is cancel_workflow_run? +

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 cancel_workflow_run? +

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.

How do I block cancel_workflow_run completely? +

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.

What MCP server provides cancel_workflow_run? +

cancel_workflow_run is provided by the GitHub Repos Manager MCP Server MCP server (kurdin/github-repos-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub Repos Manager MCP Server tool call.

Start from GitHub Repos Manager MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

84 GitHub Repos Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.