Add a comment to a Jira issue
AI agents use addCommentToJiraIssue to create or update resources in Atlassian Multi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian Multi environment.
This tool creates new content (a comment) in a Jira issue, which is a write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). Comments can be edited or deleted afterward, making this reversible.
From the tool's definition 'Add a comment to a Jira issue' - the tool creates new comment data that is persisted in Jira, modifying the issue's state reversibly.
Attacks that exploit this kind of access
Add a comment to a Jira issue. It is categorised as a Write tool in the Atlassian Multi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for addCommentToJiraIssue: 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 Atlassian Multi. Nothing to install.
addCommentToJiraIssue 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 addCommentToJiraIssue 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 addCommentToJiraIssue. 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.
addCommentToJiraIssue is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-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 →