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-docker/issue-comment.md
What issue-comment does on Docker
AI agents use issue-comment to create or update resources in Docker, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docker environment.
Why issue-comment is rated Medium
The tool performs reversible write operations (add and edit) combined with delete operations (remove comments). While deletion of comments could be considered destructive, the primary purpose appears to be collaborative issue management where edits and deletions are common, recoverable operations in most version control systems.
From the tool's definition Tool description explicitly states it 'Adds, edits, or deletes a comment on an issue' — these are create, modify, and delete operations on issue comments.
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 Docker, 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 Docker, 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 Docker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docker 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 Docker. 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 Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
This server
Across the catalogue