merge-pull-request · GitHub Enterprise MCP Server MCP

WHAT IT DOES

What merge-pull-request does on GitHub Enterprise MCP Server

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

WHY IT NEEDS A POLICY

Why merge-pull-request needs a policy

Merging a pull request creates and modifies code in the target branch (typically main/master), making it a Write action. While not immediately destructive (the original branch persists), it permanently alters the canonical codebase and can introduce bugs or security issues if the merged code is malicious.

From the tool's definition Tool name 'merge-pull-request' and description 'Merge a pull request' indicate modification of repository state by combining code branches. This is a write operation that modifies the main codebase.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge-pull-request Rate-limited

merge-pull-request 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-pull-request": {
      "limits": [
        {
          "counter": "merge-pull-request_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 Enterprise MCP Server, 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 Write tool in the GitHub Enterprise 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-pull-request? +

Register the GitHub Enterprise MCP Server 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 Enterprise MCP Server. Nothing to install.

What risk level is merge-pull-request? +

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

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 Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.