Submit a review on a pull request. Can approve, request changes, or leave a comment. Supports inline code comments.
AI agents use review_pull_request to create or update resources in Mcp Github — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Github environment.
This tool writes a review to a pull request, which can approve or block merges. While reversible in principle (reviews can be dismissed), approving a PR can trigger auto-merge pipelines and have significant downstream consequences. It modifies PR state and can influence CI/CD workflows, making it high severity.
From the tool's definition Submit a review on a pull request. Can approve, request changes, or leave a comment.
Attacks that exploit this kind of access
Submit a review on a pull request. Can approve, request changes, or leave a comment. Supports inline code comments. It is categorised as a Write tool in the Mcp Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Github MCP server in PolicyLayer and add a rule for review_pull_request: 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 Mcp Github. Nothing to install.
review_pull_request 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 review_pull_request 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 review_pull_request. 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.
review_pull_request is provided by the Mcp Github MCP server (sheeryn123/mcp-github-server). 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 →