New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

add_issue_comment

Add a comment to an issue or pull request.

SERVERGitHub SOURCE@abhishekmcp/github
Medium RISK CLASS
Category Write
Parameters 44 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-abhishekkumar2021-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.

ParameterTypeRequiredDescription
body string Yes
repo string Yes Repository name
owner string Yes Repository owner (user or org)
number integer Yes

Parameters from the server's own tool schema.

Why add_issue_comment is rated Medium

This tool creates new content (a comment) on GitHub, modifying an issue or PR in a way that persists and is visible to others. However, it is not destructive (comments are not permanently deleted by this action), not financial, and not code execution.

From the tool's definition Tool description states 'Add a comment to an issue or pull request.' The verb 'Add' indicates creation of new data (a comment). This is reversible—comments can be edited or deleted later.

Risk signalsAccepts raw HTML/template content (body)

Questions about add_issue_comment

What does the add_issue_comment tool do? +

Add a comment to an issue or pull request. 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_issue_comment accept? +

add_issue_comment accepts 4 parameters: body, repo, owner, number. Required: body, repo, owner, number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_issue_comment? +

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.

What risk level is add_issue_comment? +

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

Can I rate-limit add_issue_comment? +

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.

How do I block add_issue_comment completely? +

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.

What MCP server provides add_issue_comment? +

add_issue_comment is provided by the GitHub MCP server (@abhishekmcp/github). 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GitHub's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.