jira_clone_ticket · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_clone_ticket does on Jira MCP Server

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

This tool creates a new Jira ticket by duplicating an existing one. Creation of new data is a Write operation. It is reversible (the cloned ticket can be deleted). The blast radius is medium since an agent could spam-create many duplicate tickets, cluttering the project, but no data is irreversibly destroyed.

From the tool's definition Clone/duplicate a Jira ticket. Creates a new ticket with the same summary, description, priority, labels, and components.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_clone_ticket Rate-limited

jira_clone_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": {
    "jira_clone_ticket": {
      "limits": [
        {
          "counter": "jira_clone_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 jira_clone_ticket

What does the jira_clone_ticket tool do? +

Clone/duplicate a Jira ticket. Creates a new ticket with the same summary, description, priority, labels, and components. Optionally links the clone to the original. 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_clone_ticket? +

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

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

Can I rate-limit jira_clone_ticket? +

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

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

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