Adds a comment to an existing Jira issue. You can also control the visibility of the comment.
AI agents use add_jira_comment to create or update resources in Mcp Atlassian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Atlassian environment.
Adding a comment creates new data within a Jira issue and is reversible (comments can typically be edited or deleted). This is a Write operation rather than Read (retrieves data) or Execute (runs arbitrary code).
From the tool's definition Tool description states it 'Adds a comment to an existing Jira issue' — this is a create operation that modifies an issue by adding new content. The mention of controlling 'visibility of the comment' indicates additional write-level control over data state.
Attacks that exploit this kind of access
Adds a comment to an existing Jira issue. You can also control the visibility of the comment. It is categorised as a Write tool in the Mcp Atlassian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Atlassian MCP server in PolicyLayer and add a rule for add_jira_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 Atlassian. Nothing to install.
add_jira_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 add_jira_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 add_jira_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.
add_jira_comment is provided by the Mcp Atlassian MCP server (mcp-atlassian). 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 →