pr-close · Python MCP: Risk & Policy

WHAT IT DOES

What pr-close does on Python

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

WHY IT NEEDS A POLICY

Why pr-close needs a policy

Closing a PR is a Write operation: it modifies the PR state reversibly (PRs can be reopened). The optional branch deletion is a side effect, but the primary operation is state modification rather than irreversible destruction.

From the tool's definition Tool 'closes a pull request with an optional comment and optional branch deletion' - these are reversible modifications to PR state and repository branches.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pr-close Rate-limited

pr-close 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-close": {
      "limits": [
        {
          "counter": "pr-close_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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-close

What does the pr-close tool do? +

Closes a pull request with an optional comment and optional branch deletion. Returns structured data with PR number, state, URL, and deleted-branch flag. It is categorised as a Write tool in the Python 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-close? +

Register the Python MCP server in PolicyLayer and add a rule for pr-close: 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-close? +

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

Can I rate-limit pr-close? +

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

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

pr-close 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-close 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 →