Adds a comment to an issue. Supports visibility restrictions for groups or roles. Comment format is controlled by the "format" parameter (default: markdown). Returns the created comment with author details and timestamp.
AI agents use jira_add_comment to create or update resources in Mcp Jira Stdio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira Stdio environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Comment body text |
format | string | — | Comment format: "markdown" (converts Markdown to ADF), "adf" (use as-is ADF object), "plain" (converts plain text to ADF with basic formatting). Default: "markd |
issueKey | string | Yes | Issue key to add comment to |
visibility | object | — | Comment visibility restrictions |
Parameters from the server's own tool schema.
Adding a comment is a write operation that creates new data in Jira reversibly (comments can be edited or deleted). While comments may be visible to others and could have moderate collaborative impact, the action itself is not destructive, does not execute code, and does not move money.
From the tool's definition Tool name 'jira_add_comment' and description 'Adds a comment to an issue' indicate creation of new data. The description explicitly states it 'Returns the created comment', confirming a write operation that creates reversible content.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
Adds a comment to an issue. Supports visibility restrictions for groups or roles. Comment format is controlled by the "format" parameter (default: markdown). Returns the created comment with author details and timestamp. It is categorised as a Write tool in the Mcp Jira Stdio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
jira_add_comment accepts 4 parameters: body, format, issueKey, visibility. Required: body, issueKey. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio 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 Mcp Jira Stdio. 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 Mcp Jira Stdio MCP server (mcp-jira-stdio). 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 →