pr-merge

Merges a pull request by number, URL, or branch. Returns structured data with merge status, method, URL, and branch deletion status.

SERVERSearch SOURCEDave-London/Pare

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-pare-search/pr-merge.md

WHAT IT DOES

What pr-merge does on Search

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

RISK

Why pr-merge is rated Medium

Merging a pull request creates a new merge commit and modifies the repository state by integrating code changes into a target branch. While it can include branch deletion (which touches on destructive operations), the primary operation is a reversible write that modifies repository history through a merge commit.

From the tool's definition Tool description states it 'Merges a pull request' which is a modification operation. The return data includes 'merge status, method, URL, and branch deletion status' indicating it performs git merge operations and can delete branches.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pr-merge safely

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

pr-merge Rate-limited

pr-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": {
    "pr-merge": {
      "limits": [
        {
          "counter": "pr-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 Search, apply this rule, and every pr-merge call is checked against it from then on.

FAQ

Questions about pr-merge

What does the pr-merge tool do? +

Merges a pull request by number, URL, or branch. Returns structured data with merge status, method, URL, and branch deletion status. It is categorised as a Write tool in the Search MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pr-merge? +

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

What risk level is pr-merge? +

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

Can I rate-limit pr-merge? +

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

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

pr-merge is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Search, and thousands of servers like it.

This server

All 202 Search tools →

Across the catalogue

The MCP Attack Database →

Guides

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