List and filter repository pull requests
AI agents call list_pull_requests to retrieve information from Server Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
base | string | — | Filter by base branch name |
head | string | — | Filter by head user or head organization and branch name |
page | number | — | Page number of the results |
repo | string | Yes | Repository name |
sort | string | — | What to sort results by |
owner | string | Yes | Repository owner (username or organization) |
state | string | — | State of the pull requests to return |
per_page | number | — | Results per page (max 100) |
direction | string | — | The direction of the sort |
Parameters from the server's own tool schema.
This tool retrieves and filters existing pull request data without creating, modifying, deleting, or executing any operations. It is a read-only operation that has no side effects on the repository or its contents.
From the tool's definition Tool name 'list_pull_requests' and description 'List and filter repository pull requests' indicate a query/retrieval operation with no modification capability.
Attacks that exploit this kind of access
List and filter repository pull requests. It is categorised as a Read tool in the Server Github MCP Server, which means it retrieves data without modifying state.
list_pull_requests accepts 9 parameters: base, head, page, repo, sort, owner, state, per_page, direction. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the Server 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 Server 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 Server Github MCP server (@iflow-mcp/server-github). 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 →