AI agents use jira_comments 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.
This tool enables both retrieval (Read) and creation (Write) of comments. Since it spans categories and Write is more severe than Read, it is classified as Write. Severity is medium because while comments can be created and cause minor state changes, they are reversible and have limited blast radius compared to destructive or financial operations.
From the tool's definition Tool description states 'Get or add comments on a Jira issue.' The 'add comments' capability modifies issue state by appending comment data, which is reversible (comments can be deleted/edited).
Documented attack patterns abuse exactly the kind of access jira_comments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_comments:
{
"version": "1",
"default": "deny",
"tools": {
"jira_comments": {
"limits": [
{
"counter": "jira_comments_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}jira_comments 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.
Get or add comments on 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 jira_comments: 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.
jira_comments 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_comments 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_comments. 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_comments is provided by the Jira MCP Server MCP server (pdogra1299/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira MCP Server, 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.
6 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.