Merge a pull request
AI agents use merge_pull_request to create or update resources in Server Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Server Github environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Repository name |
owner | string | Yes | Repository owner (username or organization) |
pull_number | number | Yes | Pull request number |
commit_title | string | — | Title for the automatic commit message |
merge_method | string | — | Merge method to use |
commit_message | string | — | Extra detail to append to automatic commit message |
Parameters from the server's own tool schema.
Merging a pull request creates commits, updates branch pointers, and modifies the repository's code history in a way that is reversible (can be reverted), but has significant blast radius—an AI agent merging malicious code could compromise a repository's integrity, introduce vulnerabilities, or disrupt development workflows.
From the tool's definition Tool name 'merge_pull_request' and description 'Merge a pull request' indicate modifying repository state by integrating code changes.
Attacks that exploit this kind of access
Merge a pull request. It is categorised as a Write tool in the Server 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, pull_number, commit_title, merge_method, commit_message. Required: repo, owner, pull_number. The full parameter table on this page comes from the server's own tool schema.
Register the Server 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 Server 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 Server Github MCP server (@iflow-mcp/server-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →