add_reply_to_pull_request_comment

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/add-reply-to-pull-request-comment.md

WHAT IT DOES

What add_reply_to_pull_request_comment does on GitHub

AI agents use add_reply_to_pull_request_comment 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 reply
`repo`	string	—	Repository name
`owner`	string	—	Repository owner
`commentId`	number	—	The ID of the comment to reply to
`pullNumber`	number	—	Pull request number

Parameters from the server's own tool schema.

RISK

Why add_reply_to_pull_request_comment is rated Medium

This tool creates new data (a reply comment) in a reversible manner. While comments can be edited or deleted afterward, the primary action is write/create. The severity is medium because a malicious agent could spam comments, disrupt collaboration, or post harmful content to a repository, but the blast radius is limited to comment-level impact rather than code execution or data destruction.

From the tool's definition Tool description states it "creates a new comment" on a pull request, which is a reversible creation of data. The action is explicitly generative (adds/creates) rather than destructive, and does not execute code or move funds.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_reply_to_pull_request_comment 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_reply_to_pull_request_comment, this is the rule to start with:

add_reply_to_pull_request_comment Rate-limited

add_reply_to_pull_request_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": {
    "add_reply_to_pull_request_comment": {
      "limits": [
        {
          "counter": "add_reply_to_pull_request_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 GitHub, apply this rule, and every add_reply_to_pull_request_comment call is checked against it from then on.

FAQ

Questions about add_reply_to_pull_request_comment

What does the add_reply_to_pull_request_comment tool do? +

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified 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.

What parameters does add_reply_to_pull_request_comment accept? +

add_reply_to_pull_request_comment accepts 5 parameters: body, repo, owner, commentId, pullNumber. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_reply_to_pull_request_comment? +

Register the GitHub MCP server in PolicyLayer and add a rule for add_reply_to_pull_request_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 GitHub. Nothing to install.

What risk level is add_reply_to_pull_request_comment? +

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

Can I rate-limit add_reply_to_pull_request_comment? +

Yes. Add a rate_limit block to the add_reply_to_pull_request_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 add_reply_to_pull_request_comment completely? +

Set action: deny in the PolicyLayer policy for add_reply_to_pull_request_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 add_reply_to_pull_request_comment? +

add_reply_to_pull_request_comment 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.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 86 GitHub tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →reply-to-email on Meme MCP Server →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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