merge_pr · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What merge_pr does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why merge_pr needs a policy

Merging a pull request combines code branches, which is a significant write operation that modifies repository state. While it can be reversed (via revert), the merge itself is a persistent modification. The empty description lowers confidence, but the tool name strongly implies a PR merge operation. Severity is high because an AI misusing this could merge unreviewed or malicious code into a repository.

From the tool's definition Tool name 'merge_pr' on a GitHub MCP server that manages pull requests; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_pr Rate-limited

merge_pr 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": {
    "merge_pr": {
      "limits": [
        {
          "counter": "merge_pr_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about merge_pr

What does the merge_pr tool do? +

merge_pr. It is categorised as a Write tool in the GitHub 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 merge_pr? +

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

What risk level is merge_pr? +

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

Can I rate-limit merge_pr? +

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

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

merge_pr is provided by the GitHub MCP Server MCP server (rriesco/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.