merge

Merges a branch into the current branch. Supports abort, continue, and quit actions. Returns structured data with merge status, fast-forward detection, conflicts, and commit hash.

SERVERGithub SOURCE@paretools/github

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/io-github-dave-london-github/merge.md

WHAT IT DOES

What merge does on Github

AI agents use merge 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 merge is rated Medium

Merging branches modifies repository state by creating or updating commits and advancing branch pointers. While merges can be undone (via revert or reset), they represent write operations with moderate blast radius if applied to wrong branches (e.g., merging untested code into production).

From the tool's definition Tool description states it 'Merges a branch into the current branch' and 'Returns structured data with merge status, fast-forward detection, conflicts, and commit hash.' This action creates new commits and modifies the current branch—a reversible write…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs merge 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 merge, this is the rule to start with:

merge Rate-limited

merge 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": {
      "limits": [
        {
          "counter": "merge_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 merge call is checked against it from then on.

FAQ

Questions about merge

What does the merge tool do? +

Merges a branch into the current branch. Supports abort, continue, and quit actions. Returns structured data with merge status, fast-forward detection, conflicts, and commit hash. 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 merge? +

Register the Github MCP server in PolicyLayer and add a rule for merge: 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 merge? +

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

Can I rate-limit merge? +

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

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

merge is provided by the Github MCP server (@paretools/github). 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 202 Github tools →

Across the catalogue

The MCP Attack Database →

Guides

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