Get PR/MR detailed information including title, description, author, and branches
AI agents call get_pr_info 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 information about pull requests and merge requests (title, description, author, branches) without creating, modifying, or deleting any data. It is a straightforward read operation with no side effects. Even if misused by an AI agent, it only exposes existing metadata with no capability to alter state or trigger external operations.
From the tool's definition Tool name 'get_pr_info' and description 'Get PR/MR detailed information including title, description, author, and branches' indicate retrieval of metadata about pull/merge requests with no modification or side effects.
Attacks that exploit this kind of access
Get PR/MR detailed information including title, description, author, and branches. 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_info: 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_info 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_info 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_info. 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_info 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 →