pr-comment
Adds, edits, or deletes a comment on a pull request. Returns structured data with the comment URL, operation type, comment ID, and body echo.
This record as markdown: /tools/io-github-dave-london-git/pr-comment.md
What pr-comment does on Git
AI agents use pr-comment to create or update resources in Git, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git environment.
Why pr-comment is rated Medium
This tool creates, modifies, or removes comments on pull requests, which are reversible write operations on version control metadata. While it affects collaboration and visibility, it does not delete code repositories (which would be Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Tool description explicitly states it 'Adds, edits, or deletes a comment on a pull request.' The operations are reversible (comments can be edited or deleted), and the tool modifies pull request data without destroying underlying code or infrastructure.
Attacks that exploit this kind of access
The rule that runs pr-comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pr-comment, this is the rule to start with:
pr-comment 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 Git, apply this rule, and every pr-comment call is checked against it from then on.
Questions about pr-comment
Adds, edits, or deletes a comment on a pull request. Returns structured data with the comment URL, operation type, comment ID, and body echo. It is categorised as a Write tool in the Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Git MCP server in PolicyLayer and add a rule for pr-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 Git. Nothing to install.
pr-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 pr-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 pr-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.
pr-comment is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
This server
Across the catalogue