pull_request_read
Get information on a specific pull request in GitHub repository.
This record as markdown: /tools/github/pull-request-read.md
What pull_request_read does on GitHub
AI agents call pull_request_read to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number for pagination (min 1) |
repo | string | — | Repository name |
owner | string | — | Repository owner |
method | string | — | Action to specify what pull request data needs to be retrieved from GitHub. Possible options: 1. get - Get details of a specific pull request. 2. get_diff - |
perPage | number | — | Results per page for pagination (min 1, max 100) |
pullNumber | number | — | Pull request number |
Parameters from the server's own tool schema.
Why pull_request_read is rated Low
This tool retrieves pull request data without creating, modifying, or deleting any resources. It is a read-only operation that queries existing GitHub data, consistent with the Read category (search, list, get, fetch).
From the tool's definition Tool name is 'pull_request_read' and description states 'Get information on a specific pull request' — purely retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs pull_request_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pull_request_read, this is the rule to start with:
pull_request_read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every pull_request_read call is checked against it from then on.
Questions about pull_request_read
Get information on a specific pull request in GitHub repository. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
pull_request_read accepts 6 parameters: page, repo, owner, method, perPage, pullNumber. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for pull_request_read: 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. Nothing to install.
pull_request_read 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 pull_request_read 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 pull_request_read. 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.
pull_request_read is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue