This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jira-add-comment.md
What jira_add_comment does on UnClick
AI agents use jira_add_comment to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Comment text |
site | string | Yes | Jira site (e.g. mycompany) |
email | string | Yes | Atlassian account email |
api_token | string | Yes | Atlassian API token |
issue_key | string | Yes | Issue key (e.g. ENG-123) |
Parameters from the server's own tool schema.
Why jira_add_comment is rated Medium
Adding a comment to a Jira issue creates new data within the issue tracker but does not execute arbitrary code, delete data, or affect financial systems. It is reversible (comments can be edited or deleted). The severity is medium because misuse could spam issues, pollute audit trails, or impersonate users, but the blast radius is limited to comment-level disruption within a single issue tracking system.
From the tool's definition Tool is named 'jira_add_comment' and described as 'Add a comment to a Jira issue.' The verb 'add' indicates creation of new content (a comment) on an existing issue, which is a reversible modification.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs jira_add_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_add_comment, this is the rule to start with:
jira_add_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 UnClick, apply this rule, and every jira_add_comment call is checked against it from then on.
Questions about jira_add_comment
Add a comment to a Jira issue. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
jira_add_comment accepts 5 parameters: body, site, email, api_token, issue_key. Required: body, site, email, api_token, issue_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for jira_add_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 UnClick. Nothing to install.
jira_add_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 jira_add_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 jira_add_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.
jira_add_comment is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue