This record as markdown: /tools/dkeeno-github-mcp-server/github-review-pr.md
What github_review_pr does on Github
AI agents use github_review_pr to create or update resources in Github, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Github environment.
Why github_review_pr is rated Medium
Submitting a PR review is a write operation that creates new data (review records) on GitHub. It modifies the PR's state and history reversibly—reviews can be dismissed or edited. It does not execute code, delete data, or move money. While it affects workflow (may block/unblock merging), the action itself is fundamentally about creating/recording a review, making it Write rather than Execute.
From the tool's definition 'Submit a review on a PR' - this action creates a new review record on an existing pull request, which modifies state on GitHub by adding a review comment/approval/rejection.
Attacks that exploit this kind of access
The rule that runs github_review_pr safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_review_pr, this is the rule to start with:
github_review_pr 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 Github, apply this rule, and every github_review_pr call is checked against it from then on.
Questions about github_review_pr
Submit a review on a PR. It is categorised as a Write tool in the Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Github MCP server in PolicyLayer and add a rule for github_review_pr: 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 Github. Nothing to install.
github_review_pr 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 github_review_pr 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 github_review_pr. 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.
github_review_pr is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
This server
Across the catalogue