Add a review comment to a pull request or reply to an existing comment
AI agents use add_pull_request_review_comment to create or update resources in GitHub See MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub See MCP Server environment.
This tool creates or appends review comments to pull requests, which are reversible modifications to repository data. While it could be misused to spam, post misleading code review feedback, or inject malicious commentary that delays legitimate development work, these effects are non-destructive and can be undone by deleting the comment. This places it in the Write category rather than Destructive.
From the tool's definition Tool description states 'Add a review comment to a pull request or reply to an existing comment' — this creates new comment data within a pull request review, a reversible write operation.
Attacks that exploit this kind of access
Add a review comment to a pull request or reply to an existing comment. It is categorised as a Write tool in the GitHub See MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub See MCP Server MCP server in PolicyLayer and add a rule for add_pull_request_review_comment: 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 See MCP Server. Nothing to install.
add_pull_request_review_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_pull_request_review_comment 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 add_pull_request_review_comment. 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.
add_pull_request_review_comment is provided by the GitHub See MCP Server MCP server (jesusmaster/github-see-mcp-server). 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 →