merge_pull_request

// WHEN AI AGENTS USE THIS TOOL

AI agents use merge_pull_request to create or modify resources in GitHub. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON MERGE_PULL_REQUEST

Without a policy, an AI agent could call merge_pull_request repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach GitHub.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

github.yaml

tools:
  merge_pull_request:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full GitHub policy for all 86 tools.

// DETAILS

Tool Name merge_pull_request

Category Write

MCP Server GitHub MCP Server

Risk Level Medium

// MORE GITHUB TOOLS

Destructive delete_file Execute actions_run_trigger Execute run_secret_scanning Write add_comment_to_pending_review Write add_issue_comment Write add_reply_to_pull_request_comment Write assign_copilot_to_issue Write create_branch

View all 86 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like merge_pull_request have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the merge_pull_request tool do? +

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.

How do I enforce a policy on merge_pull_request? +

Add a rule in your Intercept YAML policy under the tools section for merge_pull_request. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the GitHub MCP server.

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

Enforce policies on GitHub