get_review_comments
Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) ...
This record as markdown: /tools/io-github-aifity-omnigit-mcp/get-review-comments.md
What get_review_comments does on GitHub
AI agents call get_review_comments 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.
Why get_review_comments is rated Low
This tool only queries and retrieves existing pull request review data. No creation, modification, deletion, or execution of code/operations occurs. The metadata flags (isResolved, isOutdated, isCollapsed) are read attributes, not write actions. Blast radius is minimal — worst case an attacker gains visibility into code review discussions, which is a Read-level confidentiality risk, not integrity or availability.
From the tool's definition Tool retrieves review threads and comments on pull requests with no modification capability. Description states 'Get review threads' and 'Returns threads with metadata and their associated comments' — purely data retrieval operations.
Attacks that exploit this kind of access
The rule that runs get_review_comments 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_review_comments, this is the rule to start with:
get_review_comments 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_review_comments call is checked against it from then on.
Questions about get_review_comments
Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for get_review_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 GitHub. Nothing to install.
get_review_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_review_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_review_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_review_comments is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.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