comment_on_ticket · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What comment_on_ticket does on Jira MCP Server

AI agents use comment_on_ticket 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 comment_on_ticket needs a policy

Adding a comment to a ticket is a reversible write operation that modifies ticket data by appending content. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial). The medium severity reflects that malicious comments could spam, harass, or spread misinformation across tracked work items, but the effect is limited to comment data and reversible by deletion.

From the tool's definition Tool name 'comment_on_ticket' and server description indicating ability to 'add comments' on Jira tickets. Sibling tools show this server manages Jira ticket operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

comment_on_ticket Rate-limited

comment_on_ticket 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": {
    "comment_on_ticket": {
      "limits": [
        {
          "counter": "comment_on_ticket_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 comment_on_ticket

What does the comment_on_ticket tool do? +

comment_on_ticket. 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 comment_on_ticket? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for comment_on_ticket: 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 comment_on_ticket? +

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

Can I rate-limit comment_on_ticket? +

Yes. Add a rate_limit block to the comment_on_ticket 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 comment_on_ticket completely? +

Set action: deny in the PolicyLayer policy for comment_on_ticket. 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 comment_on_ticket? +

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