issue-comment
Adds, edits, or deletes a comment on an issue. Returns structured data with the comment URL, operation type, comment ID, issue number, and body echo.
This record as markdown: /tools/io-github-dave-london-github/issue-comment.md
What issue-comment does on Github
AI agents use 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.
Why issue-comment is rated Medium
The tool performs reversible data modifications: adding and editing comments are clearly Write operations. Deletion of individual comments, while present, is a minor destructive aspect but doesn't escalate to the Destructive category since it's a single comment (low blast radius) and GitHub maintains audit trails.
From the tool's definition Tool description states it 'Adds, edits, or deletes a comment on an issue.' The primary operations are creating and modifying comments (Write category actions).
Attacks that exploit this kind of access
The rule that runs 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 issue-comment, this is the rule to start with:
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 issue-comment call is checked against it from then on.
Questions about issue-comment
Adds, edits, or deletes a comment on an issue. Returns structured data with the comment URL, operation type, comment ID, issue number, and body echo. 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.
Register the Github MCP server in PolicyLayer and add a rule for 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.
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 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 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.
issue-comment is provided by the Github MCP server (@paretools/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.
This server
Across the catalogue