pull_request_comment_write
Update or delete pull request review comment
This record as markdown: /tools/io-github-aifity-omnigit-mcp/pull-request-comment-write.md
What pull_request_comment_write does on GitHub
AI agents use pull_request_comment_write 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 pull_request_comment_write is rated Medium
This tool modifies pull request review comments, which are data that can be updated or removed. While 'delete' is mentioned in the description, the tool name emphasizes 'write' and the context of PR comments (which are reversible through git history and can be recreated) suggests the primary classification is Write rather than Destructive.
From the tool's definition Tool name 'pull_request_comment_write' and description 'Update or delete pull request review comment' indicate modification of existing pull request comments.
Attacks that exploit this kind of access
The rule that runs pull_request_comment_write 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 pull_request_comment_write, this is the rule to start with:
pull_request_comment_write 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 pull_request_comment_write call is checked against it from then on.
Questions about pull_request_comment_write
Update or delete pull request review comment. 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 pull_request_comment_write: 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.
pull_request_comment_write 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 pull_request_comment_write 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 pull_request_comment_write. 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.
pull_request_comment_write 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