Get PR/MR code changes (diff) with optional file extension filtering
AI agents call get_pr_changes to retrieve information from Code Review without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries pull request/merge request diffs, which is a read-only operation with no side effects. The 'Get' verb and absence of write/execute/destructive language confirm Read category. Severity is low because viewing code diffs poses minimal risk even if an AI agent misuses it—the worst outcome is information disclosure of already-shared code under review.
From the tool's definition Tool description states 'Get PR/MR code changes (diff)' — a retrieval operation with 'optional file extension filtering' for query refinement. No modification, deletion, or execution capability is mentioned.
Attacks that exploit this kind of access
Get PR/MR code changes (diff) with optional file extension filtering. It is categorised as a Read tool in the Code Review MCP Server, which means it retrieves data without modifying state.
Register the Code Review MCP server in PolicyLayer and add a rule for get_pr_changes: 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 Code Review. Nothing to install.
get_pr_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pr_changes 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 get_pr_changes. 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.
get_pr_changes is provided by the Code Review MCP server (oldjii/code-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 →