pr-reopen
Reopens a previously closed pull request, optionally with a comment. Returns structured data with PR number, state, and URL.
This record as markdown: /tools/io-github-dave-london-build/pr-reopen.md
What pr-reopen does on Build
AI agents use pr-reopen 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.
Why pr-reopen is rated Medium
This tool modifies the state of an existing pull request by reopening it (a reversible action), which is a Write operation. It does not delete data, execute code, or involve financial transactions. Severity is medium because reopening a PR could trigger CI/CD pipelines or other automated workflows, but the action itself is reversible.
From the tool's definition Reopens a previously closed pull request, optionally with a comment. Returns structured data with PR number, state, and URL.
Attacks that exploit this kind of access
The rule that runs pr-reopen 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-reopen, this is the rule to start with:
pr-reopen 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every pr-reopen call is checked against it from then on.
Questions about pr-reopen
Reopens a previously closed pull request, optionally with a comment. Returns structured data with PR number, state, and URL. 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.
Register the Build MCP server in PolicyLayer and add a rule for pr-reopen: 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.
pr-reopen is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pr-reopen 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.
Set action: deny in the PolicyLayer policy for pr-reopen. 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.
pr-reopen 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.
More on Build, and thousands of servers like it.
This server
Across the catalogue