// SCAN REPORT

GitHub Action Trigger MCP Server

5 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 30/06/2026

How to control GitHub Action Trigger MCP Server ↓

TOOL MAP

What GitHub Action Trigger MCP Server exposes to your agents

Read (3) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous GitHub Action Trigger MCP Server tools

Execute · High trigger_github_action This tool executes CI/CD pipelines and automated workflows in GitHub Actions. Write · High enable_pull_request_automerge This tool modifies PR state reversibly by enabling auto-merge configuration.

2 of GitHub Action Trigger MCP Server's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control GitHub Action Trigger MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Action Trigger MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "enable_pull_request_automerge": {
    "limits": [
      {
        "counter": "enable_pull_request_automerge_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_github_action": {
    "limits": [
      {
        "counter": "get_github_action_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register GitHub Action Trigger MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GITHUB ACTION TRIGGER →

Instant setup, no code required.

FULL CATALOGUE

All 5 GitHub Action Trigger MCP Server tools

EXECUTE 1 tools

Execute trigger_github_action Trigger a GitHub workflow dispatch event with custom inputs

WRITE 1 tools

Write enable_pull_request_automerge Enable auto-merge for a specific pull request. This will automatically merge the PR when all required checks p

READ 3 tools

Read get_github_action Get detailed information about a specific GitHub Action, including inputs and their requirements Read get_github_actions Get available GitHub Actions for a repository Read get_github_release Get the latest 2 releases from a GitHub repository

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about GitHub Action Trigger MCP Server

How do I prevent bulk modifications through GitHub Action Trigger MCP Server? +

The GitHub Action Trigger MCP Server server has 1 write tools including enable_pull_request_automerge. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach GitHub Action Trigger MCP Server.

How many tools does the GitHub Action Trigger MCP Server MCP server expose? +

5 tools across 3 categories: Execute, Read, Write. 3 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on GitHub Action Trigger MCP Server? +

Register the GitHub Action Trigger MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every GitHub Action Trigger MCP Server tool call.

Deterministic rules across all 5 GitHub Action Trigger MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GITHUB ACTION TRIGGER →

Instant setup, no code required.

5 GitHub Action Trigger MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.