get_pull_request
A PR's details (diff stats, merged state, body).
This record as markdown: /tools/io-github-abhishekkumar2021-github/get-pull-request.md
What get_pull_request does on GitHub
AI agents call get_pull_request 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 |
|---|---|---|---|
repo | string | Yes | Repository name |
owner | string | Yes | Repository owner (user or org) |
number | integer | Yes |
Parameters from the server's own tool schema.
Why get_pull_request is rated Low
This tool retrieves metadata and historical information about an existing pull request. It does not create, modify, delete, or execute any operations. The data returned (diff stats, merge state, body text) are informational only and cause no changes to the repository or any other state. Confidence is very high because the description unambiguously describes a query operation.
From the tool's definition Tool returns 'PR's details (diff stats, merged state, body)' — purely retrieval operations with no side effects. The name 'get_pull_request' and description explicitly indicate read-only data retrieval.
Attacks that exploit this kind of access
The rule that runs get_pull_request 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 get_pull_request, this is the rule to start with:
get_pull_request 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 get_pull_request call is checked against it from then on.
Questions about get_pull_request
A PR's details (diff stats, merged state, body). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_pull_request accepts 3 parameters: repo, owner, number. Required: repo, owner, number. 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 get_pull_request: 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.
get_pull_request 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 get_pull_request 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 get_pull_request. 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.
get_pull_request is provided by the GitHub MCP server (@abhishekmcp/github). 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