AI agents use add_templated_comment to create or update resources in Jira — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira environment.
This tool creates/modifies data (adds a comment to a task) in a reversible manner—comments can be edited or deleted later. It does not delete, execute code, or move money. The moderate severity reflects that mass-commenting could spam issues or inject misleading information, but the action is reversible. Confidence is high given the clear 'add' verb and explicit comment-creation functionality.
From the tool's definition Tool name contains 'add' and description states 'Add a comment using a registered template'. The operation creates new comment data in Jira.
Attacks that exploit this kind of access
Add a comment using a registered template (with variable substitution) or raw markdown. Provide exactly one of template_id or markdown. It is categorised as a Write tool in the Jira MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira MCP server in PolicyLayer and add a rule for add_templated_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. Nothing to install.
add_templated_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_templated_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_templated_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_templated_comment is provided by the Jira MCP server (softspark/jira-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 →