Update an existing comment on 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).
AI agents use update_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.
This is a Write operation because it modifies data (updates a comment) in a reversible manner. The severity is medium because unauthorized comment updates could alter project history, mislead team members, or tamper with audit trails, but the blast radius is limited to comment content on a single issue.
From the tool's definition Tool description states 'Update an existing comment on a Jira issue' - this modifies existing data reversibly.
Attacks that exploit this kind of access
Update an existing comment on 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). 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 update_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.
update_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 update_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 update_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.
update_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 →