assign_ticket · Jira MCP: Risk & Policy

WHAT IT DOES

What assign_ticket does on Jira

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

Assigning a ticket modifies ticket state by changing the assignee field, which is a Write operation. The severity is medium because misuse could redirect work items to unintended parties, causing workflow disruption and potential information access by wrong users, but it is reversible (can be re-assigned). It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).

From the tool's definition Tool name 'assign_ticket' and description 'Assign a Jira ticket to a user' indicate modification of ticket metadata (assignee field) in Jira. This is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_ticket Rate-limited

assign_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": {
    "assign_ticket": {
      "limits": [
        {
          "counter": "assign_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 assign_ticket

What does the assign_ticket tool do? +

Assign a Jira ticket to a user. 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 assign_ticket? +

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

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

Can I rate-limit assign_ticket? +

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

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

assign_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.