add_comment_to_pending_review
Add review comment to the requester's latest pending pull request review
This record as markdown: /tools/io-github-aifity-omnigit-mcp/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.
Why add_comment_to_pending_review is rated Medium
This tool creates new comment data on a pending pull request review, which is a reversible write operation. It modifies the review but doesn't execute code, delete data, or move money. Severity is medium because malicious comments could disrupt collaboration or inject misleading information, but the blast radius is limited to review comments on a single PR.
From the tool's definition add_comment_to_pending_review - creates/adds a comment to a pull request review, which modifies the review state reversibly
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. 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.
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/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