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-pare-test/issue-comment.md
What issue-comment does on Test
AI agents use issue-comment to create or update resources in Test, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Test environment.
Why issue-comment is rated Medium
This tool creates or modifies data (comments on issues) in a reversible manner. While it can delete comments, the primary operations are additive and editable. It does not permanently destroy data in a way that cannot be recovered (comments can be restored from version history in most systems), nor does it execute arbitrary code or perform financial operations.
From the tool's definition Tool description explicitly states it 'Adds, edits, or deletes a comment on an issue' and returns structured data including comment ID and body echo. The verbs 'adds' and 'edits' indicate reversible modifications to data.
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 Test, 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 Test, 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 Test MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Test 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 Test. 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 Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Test, and thousands of servers like it.
This server
Across the catalogue