List pull requests in a repository
AI agents call github_list_prs to retrieve information from AI Code Review MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists pull requests from a GitHub repository. It performs a read-only query with no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent listing PRs cannot harm data integrity or trigger external actions. Severity is low because the output is already publicly visible repository metadata.
From the tool's definition Tool name 'github_list_prs' and description 'List pull requests in a repository' indicate a query operation that retrieves data without modification. No parameters are described that would enable side effects.
Attacks that exploit this kind of access
List pull requests in a repository. It is categorised as a Read tool in the AI Code Review MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AI Code Review MCP Server MCP server in PolicyLayer and add a rule for github_list_prs: 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 AI Code Review MCP Server. Nothing to install.
github_list_prs 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 github_list_prs 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_list_prs. 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_list_prs is provided by the AI Code Review MCP Server MCP server (namph-kozocom/review-code-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 →