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.

SERVERBuild SOURCEDave-London/Pare

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/pr-comment.md

WHAT IT DOES

What pr-comment does on Build

AI agents use pr-comment to create or update resources in Build, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Build environment.

RISK

Why pr-comment is rated Medium

The tool performs reversible modifications to pull request comments: adding, editing, or deleting comments. While deletion is mentioned, it is deletion of comment objects (not data destruction in the irreversible sense of dropping databases or purging repositories), and these actions can typically be undone or recovered through version history or GitHub's audit logs.

From the tool's definition Tool description explicitly states it 'Adds, edits, or deletes a comment on a pull request.' These are write operations that modify external state (GitHub pull requests).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pr-comment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pr-comment": {
      "limits": [
        {
          "counter": "pr-comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every pr-comment call is checked against it from then on.

FAQ

Questions about pr-comment

What does the pr-comment tool do? +

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 Build MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pr-comment? +

Register the Build 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 Build. Nothing to install.

What risk level is pr-comment? +

pr-comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pr-comment? +

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.

How do I block pr-comment completely? +

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.

What MCP server provides pr-comment? +

pr-comment is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →