jira_add_comment · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_add_comment does on Jira MCP Server

AI agents use jira_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.

WHY IT NEEDS A POLICY

Why jira_add_comment needs a policy

Adding a comment to a Jira ticket is a Write operation—it creates new data that can be edited or deleted later, making it reversible. The severity is medium because misuse could spam tickets, post misleading information, or confuse stakeholders, but the impact is limited to comment-level changes without affecting core ticket state or other systems.

From the tool's definition The tool 'jira_add_comment' has a description stating 'Add a comment to a Jira ticket,' which directly indicates it creates or modifies data (a comment) in a reversible manner. The tool does not delete, destroy, or execute arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_add_comment Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_add_comment": {
      "limits": [
        {
          "counter": "jira_add_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jira MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_add_comment

What does the jira_add_comment tool do? +

Add a comment to a Jira ticket. RULES: (1) Default to a HIGH LEVEL update for stakeholders, product owners, and QA, focus on WHAT changed and the impact, not how it was built (e.g. 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.

How do I enforce a policy on jira_add_comment? +

Register the Jira MCP Server 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 Jira MCP Server. Nothing to install.

What risk level is jira_add_comment? +

jira_add_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jira_add_comment? +

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.

How do I block jira_add_comment completely? +

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.

What MCP server provides jira_add_comment? +

jira_add_comment is provided by the Jira MCP Server MCP server (rui-branco/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.