List pull requests for a repository with filtering options
AI agents call get_repository_prs to retrieve information from GitHub PR 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 queries and retrieves pull request data from a repository with optional filtering. It has no side effects—it does not create, modify, delete, or execute anything. It is purely informational retrieval, fitting the Read category.
From the tool's definition Tool is described as 'List pull requests' which is a read operation that retrieves data without modification. The name 'get_repository_prs' uses the 'get' verb indicating data retrieval.
Attacks that exploit this kind of access
List pull requests for a repository with filtering options. It is categorised as a Read tool in the GitHub PR Review MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub PR Review MCP Server MCP server in PolicyLayer and add a rule for get_repository_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 GitHub PR Review MCP Server. Nothing to install.
get_repository_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 get_repository_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 get_repository_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.
get_repository_prs is provided by the GitHub PR Review MCP Server MCP server (vibe-code-agent/github-review). 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 →