Update an existing jira ticket
AI agents use update-ticket to create or update resources in JIRA MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JIRA MCP environment.
Updating a ticket modifies existing data (summary, description, status, fields, etc.) in a reversible manner—changes can be undone or corrected. This is a write operation. Severity is medium because misuse could create confusion (wrong status updates, erroneous assignments), impact workflows, and affect team coordination, but changes remain recoverable via ticket history and rollback.
From the tool's definition Tool performs an 'Update an existing jira ticket' operation, which modifies data reversibly without deletion or destruction. The server description confirms it enables AI assistants to 'update' JIRA tickets.
Documented attack patterns abuse exactly the kind of access update-ticket gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JIRA MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update-ticket:
{
"version": "1",
"default": "deny",
"tools": {
"update-ticket": {
"limits": [
{
"counter": "update-ticket_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-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.
Free to start. No card required.
Update an existing jira ticket. It is categorised as a Write tool in the JIRA MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JIRA MCP server in PolicyLayer and add a rule for update-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. Nothing to install.
update-ticket is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-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.
Set action: deny in the PolicyLayer policy for update-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.
update-ticket is provided by the JIRA MCP server (mankowskinick/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JIRA MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 JIRA MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.