Add a comment to a Jira issue.
AI agents use add_comment to create or update resources in Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Server environment.
Adding comments is a Write operation—it creates new data that can typically be edited or deleted later, causing no permanent irreversible damage. Severity is medium because while comments are generally low-risk, they are visible to team members and could spread misinformation or sensitive data if an agent posts inappropriate content.
From the tool's definition Tool adds a comment to a Jira issue, which creates new data (comment text) and modifies the issue's state by appending information to it. The description explicitly states 'Add a comment', a reversible creation action.
Attacks that exploit this kind of access
Add a comment to a Jira issue. It is categorised as a Write tool in the Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for 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 MCP Server. Nothing to install.
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 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 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.
add_comment is provided by the Jira MCP Server MCP server (jondoesflow/mcp_server_jira). 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 →