List pull requests in a repository. State: open, closed, all.
AI agents call list_pull_requests to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that retrieves metadata about pull requests without creating, modifying, deleting, executing code, or committing financial obligations. The blast radius of accidental misuse is minimal—at worst, listing PRs could expose repository structure or recent activity, but causes no destructive harm or operational consequences.
From the tool's definition Tool is 'list_pull_requests' that 'List[s] pull requests in a repository'. No side effects or modifications occur—this retrieves and queries existing PR data across different states (open, closed, all).
Attacks that exploit this kind of access
List pull requests in a repository. State: open, closed, all. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for list_pull_requests: 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 MCP Server. Nothing to install.
list_pull_requests 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 list_pull_requests 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 list_pull_requests. 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.
list_pull_requests is provided by the GitHub MCP Server MCP server (maheshjagzap123/mcp-server). 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 →