add_comment_to_pending_review
Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).
This record as markdown: /tools/github/add-comment-to-pending-review.md
What add_comment_to_pending_review does on GitHub
AI agents use add_comment_to_pending_review to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | The text of the review comment |
line | number | — | The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range |
path | string | — | The relative path to the file that necessitates a comment |
repo | string | — | Repository name |
side | string | — | The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state |
owner | string | — | Repository owner |
startLine | number | — | For multi-line comments, the first line of the range that the comment applies to |
startSide | string | — | For multi-line comments, the starting side of the diff that the comment applies to. LEFT indicates the previous state, RIGHT indicates the new state |
pullNumber | number | — | Pull request number |
subjectType | string | — | The level at which the comment is targeted |
Parameters from the server's own tool schema.
Why add_comment_to_pending_review is rated Medium
This tool creates new comments on pull requests, which are write operations. While comments can technically be deleted, the primary action is creation/addition of data. The severity is medium because misuse could spam pull requests with unwanted comments or interfere with legitimate code review processes, but the blast radius is limited to a single pull request's review comments and can be remediated by deletion.
From the tool's definition Tool allows adding a review comment to a pending pull request review. The description indicates it 'Add[s] review comment' which creates new data (comments) on a GitHub pull request. This is a reversible modification of pull request review state.
Risk signalsAccepts raw HTML/template content (body) · Accepts file system path (path) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs add_comment_to_pending_review 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 add_comment_to_pending_review, this is the rule to start with:
add_comment_to_pending_review stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 add_comment_to_pending_review call is checked against it from then on.
Questions about add_comment_to_pending_review
Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure). It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_comment_to_pending_review accepts 10 parameters: body, line, path, repo, side, owner, startLine, startSide, pullNumber, subjectType. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for add_comment_to_pending_review: 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.
add_comment_to_pending_review 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_comment_to_pending_review 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_comment_to_pending_review. 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_comment_to_pending_review is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.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