AI agents use jira_add_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 to a Jira issue is a reversible write operation that creates new content. It modifies issue state by appending data but does not delete or execute arbitrary code. The severity is medium because misuse could pollute issue tracking with spam, misinformation, or sensitive data disclosure, affecting team collaboration and issue management integrity.
From the tool's definition Tool name 'jira_add_comment' indicates it adds/creates comments on Jira issues. The empty description prevents full certainty, but the name clearly implies a write operation that creates new data (comments) on existing issues.
Documented attack patterns abuse exactly the kind of access jira_add_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_add_comment:
{
"version": "1",
"default": "deny",
"tools": {
"jira_add_comment": {
"limits": [
{
"counter": "jira_add_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}jira_add_comment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
jira_add_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 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 MCP Atlassian. 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 MCP Atlassian MCP server (samwang0723/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 MCP Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.