enable_pull_request_automerge

WHAT IT DOES

What enable_pull_request_automerge does on GitHub Action Trigger MCP Server

AI agents use enable_pull_request_automerge to create or update resources in GitHub Action Trigger MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Action Trigger MCP Server environment.

WHY IT NEEDS A POLICY

Why enable_pull_request_automerge needs a policy

This tool modifies PR state reversibly by enabling auto-merge configuration. While it does not immediately delete data (Destructive) or move money (Financial), it creates a condition that will automatically merge code into a repository branch when checks pass.

From the tool's definition Tool description states 'Enable auto-merge for a specific pull request...will automatically merge the PR' — this modifies the state of a pull request by setting an auto-merge flag, creating a write operation that affects repository state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_pull_request_automerge Rate-limited

enable_pull_request_automerge stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "enable_pull_request_automerge": {
      "limits": [
        {
          "counter": "enable_pull_request_automerge_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub Action Trigger MCP Server, so you can run agents against it safely.

FAQ

Questions about enable_pull_request_automerge

What does the enable_pull_request_automerge tool do? +

Enable auto-merge for a specific pull request. This will automatically merge the PR when all required checks pass. It is categorised as a Write tool in the GitHub Action Trigger MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on enable_pull_request_automerge? +

Register the GitHub Action Trigger MCP Server MCP server in PolicyLayer and add a rule for enable_pull_request_automerge: 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 Action Trigger MCP Server. Nothing to install.

What risk level is enable_pull_request_automerge? +

enable_pull_request_automerge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit enable_pull_request_automerge? +

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

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

enable_pull_request_automerge is provided by the GitHub Action Trigger MCP Server MCP server (nextdriveioe/github-action-trigger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.