merge_pull_request · GitHub MCP Tools MCP: Risk & Policy

WHAT IT DOES

What merge_pull_request does on GitHub MCP Tools

AI agents invoke merge_pull_request to trigger actions in GitHub MCP Tools. 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.

WHY IT NEEDS A POLICY

Why merge_pull_request needs a policy

Merging a pull request is an Execute-level action: it runs an integration operation on GitHub that modifies branch history and can trigger downstream workflows. While technically not fully irreversible (a revert commit is possible), the merge itself cannot be undone cleanly, and misuse could introduce bad code into production branches.

From the tool's definition 'Merge a pull request' — merging integrates code changes into a target branch, triggering side effects (CI/CD pipelines, branch updates, commit history changes) that are difficult to reverse without additional action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_pull_request Rate-limited

merge_pull_request 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": {
    "merge_pull_request": {
      "limits": [
        {
          "counter": "merge_pull_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 MCP Tools, so you can run agents against it safely.

FAQ

Questions about merge_pull_request

What does the merge_pull_request tool do? +

Merge a pull request. It is categorised as a Execute tool in the GitHub MCP Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on merge_pull_request? +

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

What risk level is merge_pull_request? +

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

Can I rate-limit merge_pull_request? +

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

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

merge_pull_request is provided by the GitHub MCP Tools MCP server (pranesh-2005/usingmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.