Get the review comments on a pull request
AI agents call get_pull_request_comments 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 |
|---|---|---|---|
repo | string | Yes | Repository name |
owner | string | Yes | Repository owner (username or organization) |
pull_number | number | Yes | Pull request number |
Parameters from the server's own tool schema.
This tool retrieves existing pull request review comments from GitHub, which is a read-only query operation. It does not create, modify, delete, or execute any actions. The blast radius is minimal—unauthorized access could expose comments that may contain sensitive information, but this is limited to viewing already-public or accessible repository data.
From the tool's definition Tool name 'get_pull_request_comments' and description 'Get the review comments on a pull request' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get the review comments on a pull request. It is categorised as a Read tool in the Server Github MCP Server, which means it retrieves data without modifying state.
get_pull_request_comments accepts 3 parameters: repo, owner, pull_number. Required: repo, owner, pull_number. 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 get_pull_request_comments: 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.
get_pull_request_comments 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_comments 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_comments. 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_comments 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 →