List pull requests from a repository
AI agents call list_repositories_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 read-only operation that retrieves pull request information from a repository. It performs a query with no ability to create, modify, delete, or execute operations. The blast radius if misused is minimal—an agent could only gain visibility into pull request data already accessible to the authenticated user.
From the tool's definition Tool name 'list_repositories_pull_requests' and description 'List pull requests from a repository' indicate querying/retrieving pull request data with no modification or side effects.
Attacks that exploit this kind of access
List pull requests from a repository. 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_repositories_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_repositories_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_repositories_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_repositories_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_repositories_pull_requests is provided by the Github MCP Server MCP server (parassolanki/github-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 →