Add a comment to an existing issue
AI agents use add_issue_comment to create or update resources in Helm Chart CLI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Helm Chart CLI environment.
This tool creates new content (a comment) attached to an existing issue resource, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The severity is medium because malicious comments could spam, mislead, or harass users, but the effect is limited and reversible.
From the tool's definition Tool name 'add_issue_comment' and description 'Add a comment to an existing issue' indicate modification of existing data (appending a comment to an issue).
Attacks that exploit this kind of access
Add a comment to an existing issue. It is categorised as a Write tool in the Helm Chart CLI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Helm Chart CLI 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 Helm Chart CLI. 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 Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →