get_pull_request_comments

List pull request review comments (inline comments on the diff). For general PR conversation comments, use list_issue_comments with the PR number.

Server Mcp Github @missionsquad/mcp-github
Category Read
Risk class Low
Parameters 00 required

What get_pull_request_comments does on Mcp Github

AI agents call get_pull_request_comments to retrieve information from Mcp Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_pull_request_comments needs a policy

This tool retrieves and lists existing pull request comments without modifying, creating, deleting, or executing any operations. It is a pure read operation that queries GitHub API data. The low severity reflects minimal blast radius if misused by an AI agent—at worst, it exposes public repository comments that are already accessible to authorized users.

From the tool's definition Tool name is 'get_pull_request_comments' and description states 'List pull request review comments' — the verb 'List' and 'get' indicate retrieval/query operations with no side effects.

Questions about get_pull_request_comments

What does the get_pull_request_comments tool do? +

List pull request review comments (inline comments on the diff). For general PR conversation comments, use list_issue_comments with the PR number. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pull_request_comments? +

Register the Mcp 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 Mcp Github. Nothing to install.

What risk level is get_pull_request_comments? +

get_pull_request_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pull_request_comments? +

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.

How do I block get_pull_request_comments completely? +

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.

What MCP server provides get_pull_request_comments? +

get_pull_request_comments is provided by the Mcp Github MCP server (@missionsquad/mcp-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.