create_ticket · Jira MCP: Risk & Policy

WHAT IT DOES

What create_ticket does on Jira

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

WHY IT NEEDS A POLICY

Why create_ticket needs a policy

Creating a ticket is a reversible write operation—new data is created in Jira but can be deleted or modified later. It has medium severity because uncontrolled ticket creation could spam a Jira instance or consume quota, but the impact is bounded and recoverable. Confidence is high given explicit 'create' semantics and clear context from related tools.

From the tool's definition Tool name 'create_ticket' and description 'Create a new Jira ticket' indicate data creation. The sibling tool set includes reversible operations like add_comment, assign_ticket, and batch_create_issues, confirming this server focuses on write/create…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_ticket Rate-limited

create_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": {
    "create_ticket": {
      "limits": [
        {
          "counter": "create_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, so you can run agents against it safely.

FAQ

Questions about create_ticket

What does the create_ticket tool do? +

Create a new Jira ticket. 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.

How do I enforce a policy on create_ticket? +

Register the Jira MCP server in PolicyLayer and add a rule for create_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. Nothing to install.

What risk level is create_ticket? +

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

Can I rate-limit create_ticket? +

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

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

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