actions_run_trigger

Trigger GitHub Actions workflow operations, including running, re-running, cancelling workflow runs, and deleting workflow run logs.

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

High RISK CLASS

Category Execute

Parameters 70 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/actions-run-trigger.md

WHAT IT DOES

What actions_run_trigger does on GitHub

AI agents invoke actions_run_trigger 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.

Parameter	Type	Required	Description
`ref`	string	—	The git reference for the workflow. The reference can be a branch or tag name. Required for 'run_workflow' method.
`repo`	string	—	Repository name
`owner`	string	—	Repository owner
`inputs`	object	—	Inputs the workflow accepts. Only used for 'run_workflow' method.
`method`	string	—	The method to execute
`run_id`	number	—	The ID of the workflow run. Required for all methods except 'run_workflow'.
`workflow_id`	string	—	The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml). Required for 'run_workflow' method.

Parameters from the server's own tool schema.

RISK

Why actions_run_trigger is rated High

While the tool includes destructive operations (deleting logs), its primary purpose is to trigger/execute GitHub Actions workflows. Workflow execution is the more dangerous capability—it can execute arbitrary code with repository permissions. This is Execute-primary with destructive side effects.

From the tool's definition Tool enables 'running, re-running, cancelling workflow runs' and 'deleting workflow run logs.' Running and re-running workflows executes arbitrary code in GitHub's environment; deleting logs is an irreversible action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs actions_run_trigger 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 actions_run_trigger, this is the rule to start with:

actions_run_trigger Rate-limited

actions_run_trigger 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": {
    "actions_run_trigger": {
      "limits": [
        {
          "counter": "actions_run_trigger_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 actions_run_trigger call is checked against it from then on.

FAQ

Questions about actions_run_trigger

What does the actions_run_trigger tool do? +

Trigger GitHub Actions workflow operations, including running, re-running, cancelling workflow runs, and deleting workflow run logs. 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.

What parameters does actions_run_trigger accept? +

actions_run_trigger accepts 7 parameters: ref, repo, owner, inputs, method, run_id, workflow_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on actions_run_trigger? +

Register the GitHub MCP server in PolicyLayer and add a rule for actions_run_trigger: 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 actions_run_trigger? +

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

Can I rate-limit actions_run_trigger? +

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

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

actions_run_trigger is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). 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 86 GitHub tools → High-risk tools on this server →

Across the catalogue

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

Guides

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