pr-close

Closes a pull request with an optional comment and optional branch deletion. Returns structured data with PR number, state, URL, and deleted-branch flag.

SERVERBuild 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-build/pr-close.md

WHAT IT DOES

What pr-close does on Build

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

RISK

Why pr-close is rated Medium

Closing a pull request modifies repository state (changes PR status from open to closed) and optionally deletes a branch. While branch deletion is technically destructive, the primary action is a reversible state change (PRs can be reopened). This fits Write rather than Destructive since PR closure is reversible. However, optional branch deletion elevates severity to medium.

From the tool's definition Tool description states it 'Closes a pull request' and includes 'optional branch deletion'. Closing a PR is a state modification operation; branch deletion is destructive but presented as optional.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pr-close safely

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

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every pr-close call is checked against it from then on.

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 Build 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 Build 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 Build. 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 Build 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 Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

The MCP Attack Database →

Guides

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