add_issue_comment
Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.
This record as markdown: /tools/github/add-issue-comment.md
What add_issue_comment does on GitHub
AI agents use add_issue_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 | — | Comment content |
repo | string | — | Repository name |
owner | string | — | Repository owner |
issue_number | number | — | Issue number to comment on |
Parameters from the server's own tool schema.
Why add_issue_comment is rated Medium
This tool creates new data (comments) in a GitHub repository, which is a reversible write operation. While comments can be edited or deleted later, the primary action is creating content. Severity is medium because malicious comments could spam, harass, or spread misinformation across issues/PRs, but the blast radius is limited to comment creation without code execution, deletion, or financial impact.
From the tool's definition Tool description states 'Add a comment to a specific issue in a GitHub repository' and explicitly mentions pull requests. The verb 'add' and the action of creating new comments demonstrates data creation.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs add_issue_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_issue_comment, this is the rule to start with:
add_issue_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 GitHub, apply this rule, and every add_issue_comment call is checked against it from then on.
Questions about add_issue_comment
Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments. 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.
add_issue_comment accepts 4 parameters: body, repo, owner, issue_number. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for add_issue_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.
add_issue_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 add_issue_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 add_issue_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.
add_issue_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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue