pr-merge · Python MCP: Risk & Policy

WHAT IT DOES

What pr-merge does on Python

AI agents invoke pr-merge to trigger actions in Python. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why pr-merge needs a policy

Merging a pull request is an external operation that integrates code changes into a branch. While it can sometimes be reversed (e.g., by reverting), the merge itself is a significant external action that triggers workflows, modifies repository history, and potentially deletes branches.

From the tool's definition Merges a pull request by number, URL, or branch. Returns structured data with merge status, method, URL, and branch deletion status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pr-merge Rate-limited

pr-merge stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Python, so you can run agents against it safely.

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 Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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

Register the Python 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 Python. Nothing to install.

What risk level is pr-merge? +

pr-merge is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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 Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

pr-merge is one line of Python's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →