AI agents call list_pull_request_review_comments to retrieve information from Mcp Gmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing pull request review comments without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could retrieve comments it shouldn't see, but this is an informational leak rather than a destructive or executionally risky action. Confidence is high because the description is clear and unambiguous.
From the tool's definition Tool name and description indicate 'List review comments' — a retrieval operation with no modification or side effects. The verb 'list' is explicitly a Read operation.
Attacks that exploit this kind of access
List review comments for a pull request. It is categorised as a Read tool in the Mcp Gmail MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for list_pull_request_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 Mcp Gmail. Nothing to install.
list_pull_request_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 list_pull_request_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 list_pull_request_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.
list_pull_request_review_comments is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →