AI agents use pr_merge to create or update resources in Pr Review — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pr Review environment.
An AI agent can call pr_merge faster than any human can review — one bad instruction and it creates or modifies resources in Pr Review by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Merge a pull request. Uses interactive elicitation for confirmation when supported, falls back to confirm=true parameter. It is categorised as a Write tool in the Pr Review MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pr Review 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 Pr Review. Nothing to install.
pr_merge 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_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.
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.
pr_merge is provided by the Pr Review MCP server (thebtf/pr-review-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →