AI agents use jira_add_comment to create or update resources in Jira Dev — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira Dev environment.
The tool creates new comment data on Jira issues, which is a Write operation—it modifies state but is reversible (comments can be edited or deleted). Severity is medium because misuse could spam issues, create misleading comments, or pollute project communication, but the impact is contained to comment-level data and does not expose financial systems or enable destructive operations.
From the tool's definition Tool description states 'Post a comment on a Jira issue', which is a create/add operation that modifies issue data reversibly.
Attacks that exploit this kind of access
Post a comment on a Jira issue. Returns the comment URL so you can verify it directly. It is categorised as a Write tool in the Jira Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira Dev 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 Jira Dev. 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 Jira Dev MCP server (jira-dev-mcp). 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 →