List pull requests in a GitHub repository with filtering by state, head/base branch, and sorting options.
AI agents call list_pull_requests to retrieve information from Mcp Github 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 data with filtering and sorting capabilities. It has no side effects—it does not create, modify, delete, or execute operations. It is a pure read operation that returns information from the GitHub repository. Blast radius is minimal since misuse only results in data retrieval.
From the tool's definition Tool name 'list_pull_requests' and description 'List pull requests in a GitHub repository with filtering by state, head/base branch, and sorting options' indicate query/retrieval operations only.
Attacks that exploit this kind of access
List pull requests in a GitHub repository with filtering by state, head/base branch, and sorting options. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.
Register the Mcp Github 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 Mcp Github. 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 Mcp Github MCP server (sheeryn123/mcp-github-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 →