Add a comment to a Jira issue. Supports plain text or Markdown for rich formatting (headings, lists, code blocks, links, etc.). Markdown is automatically converted to ADF. For mentions, use format: @[accountId:displayName] (get accountId from get_users tool). Returns comment ID and creation details.
AI agents use create_comment to create or update resources in Raalarcon Jira — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Raalarcon Jira environment.
Creating a comment is a write operation that adds new data to a Jira issue reversibly. While it modifies the issue state, the action is not destructive—comments can be edited or deleted. It does not execute code, trigger financial transactions, or irreversibly delete data. The low severity reflects minimal blast radius: misuse would result in unwanted comments rather than data loss or system compromise.
From the tool's definition Tool description states 'Add a comment to a Jira issue' and 'Returns comment ID and creation details', indicating content creation that is reversible (comments can be deleted via the sibling delete_comment tool).
Attacks that exploit this kind of access
Add a comment to a Jira issue. Supports plain text or Markdown for rich formatting (headings, lists, code blocks, links, etc.). Markdown is automatically converted to ADF. For mentions, use format: @[accountId:displayName] (get accountId from get_users tool). Returns comment ID and creation details. It is categorised as a Write tool in the Raalarcon Jira MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Raalarcon Jira MCP server in PolicyLayer and add a rule for create_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 Raalarcon Jira. Nothing to install.
create_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 create_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 create_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.
create_comment is provided by the Raalarcon Jira MCP server (raalarcon-jira-mcp-server). 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 →