merge_pull_request
Merge a pull request in a GitHub repository.
This record as markdown: /tools/github/merge-pull-request.md
What merge_pull_request does on GitHub
AI agents use merge_pull_request 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | — | Repository name |
owner | string | — | Repository owner |
pullNumber | number | — | Pull request number |
commit_title | string | — | Title for merge commit |
merge_method | string | — | Merge method |
commit_message | string | — | Extra detail for merge commit |
Parameters from the server's own tool schema.
Why merge_pull_request is rated Medium
Merging a pull request modifies the repository by integrating code changes into a target branch. This is a reversible operation (merges can be reverted), so it falls under Write rather than Destructive. However, severity is high because a malicious merge could introduce malicious code, break builds, or compromise production branches, affecting many users and requiring significant remediation effort.
From the tool's definition Tool name 'merge_pull_request' and description 'Merge a pull request in a GitHub repository' indicate modification of repository state by combining code branches.
Attacks that exploit this kind of access
The rule that runs merge_pull_request 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_pull_request, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every merge_pull_request call is checked against it from then on.
Questions about merge_pull_request
Merge a pull request in a GitHub repository. 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.
merge_pull_request accepts 6 parameters: repo, owner, pullNumber, commit_title, merge_method, commit_message. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub 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. Nothing to install.
merge_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
merge_pull_request is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue