AI agents use jira_add_comment to create or update resources in Jiraxmcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jiraxmcp environment.
Adding a comment creates data reversibly (comments can be edited or deleted), so it fits the Write category rather than Read (which would be view-only) or Destructive (which would be irreversible). Severity is medium because while comments are not critical data, an AI agent could spam, harass, or create misleading information in issues affecting team coordination.
From the tool's definition Tool description states 'Add a comment to a Jira issue' — this creates new data (a comment) that is persisted in Jira and can be modified or deleted later, making it a Write operation.
Attacks that exploit this kind of access
Add a comment to a Jira issue. It is categorised as a Write tool in the Jiraxmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jirax 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 Jiraxmcp. 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 Jirax MCP server (vaibhavpandeyvpz/jiraxmcp). 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 →