cancel_action_run

Cancel a pending or running Actions workflow run

SERVERForgejo SOURCEsqcows/forgejo-mcp

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/sqcows-forgejo-mcp/cancel-action-run.md

WHAT IT DOES

What cancel_action_run does on Forgejo

AI agents invoke cancel_action_run to trigger actions in Forgejo. 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 cancel_action_run is rated High

Cancelling a workflow run terminates active CI/CD processes, disrupting deployments or builds.

From the tool's definition Cancel a pending or running Actions workflow run

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cancel_action_run safely

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

cancel_action_run Rate-limited

cancel_action_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": {
    "cancel_action_run": {
      "limits": [
        {
          "counter": "cancel_action_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 Forgejo, apply this rule, and every cancel_action_run call is checked against it from then on.

FAQ

Questions about cancel_action_run

What does the cancel_action_run tool do? +

Cancel a pending or running Actions workflow run. It is categorised as a Execute tool in the Forgejo 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_action_run? +

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

What risk level is cancel_action_run? +

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

Can I rate-limit cancel_action_run? +

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

Set action: deny in the PolicyLayer policy for cancel_action_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_action_run? +

cancel_action_run is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →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 →