github_merge_pr

A write tool on the Github MCP server.

SERVERGithub SOURCEdkeeno/github-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-merge-pr.md

WHAT IT DOES

What github_merge_pr does on Github

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

RISK

Why github_merge_pr is rated Medium

Merging a PR creates commits and modifies repository state, making it a Write action rather than Read. It is not Destructive because reverts are possible. The high severity reflects that unintended merges could corrupt production code or introduce security vulnerabilities. Confidence is slightly reduced (0.85) because the tool description is empty, requiring inference from the name and server context.

From the tool's definition Tool name 'github_merge_pr' indicates merging pull requests. The server description states it enables 'push, releases, issues, PRs' operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_merge_pr safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_merge_pr, this is the rule to start with:

github_merge_pr Rate-limited

github_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": {
    "github_merge_pr": {
      "limits": [
        {
          "counter": "github_merge_pr_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every github_merge_pr call is checked against it from then on.

FAQ

Questions about github_merge_pr

What does the github_merge_pr tool do? +

github_merge_pr is a write tool on the Github MCP server. It is categorised as a Write tool in the Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_merge_pr? +

Register the Github MCP server in PolicyLayer and add a rule for github_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. Nothing to install.

What risk level is github_merge_pr? +

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

Can I rate-limit github_merge_pr? +

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

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

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

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 69 Github tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →