Fetch review thread comments (diff comments) for a pull request.
AI agents call github_review_get_review_comments to retrieve information from Promethean OS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing pull request review comments without creating, modifying, or deleting any data. It is a read-only query operation on GitHub pull request metadata. The blast radius of misuse is minimal — an attacker could only view comments they may not have authorization for, not alter repository state or trigger external actions.
From the tool's definition Tool name contains 'get' and description states 'Fetch review thread comments' — both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Fetch review thread comments (diff comments) for a pull request. It is categorised as a Read tool in the Promethean OS MCP MCP Server, which means it retrieves data without modifying state.
Register the Promethean OS MCP server in PolicyLayer and add a rule for github_review_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 Promethean OS MCP. Nothing to install.
github_review_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 github_review_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 github_review_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.
github_review_get_review_comments is provided by the Promethean OS MCP server (octave-commons/mcp). 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 →