AI agents use update_ticket to create or update resources in Tickr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
scope | string | — | |
title | string | — | |
number | string | Yes | Ticket display number, e.g. 'TKR-42' (legacy) or 'TKR-BUG-0042' (typed) |
status | string | — | New status slug |
content | string | — | |
assignee | string | — | Username or 'unassigned' |
due_date | string | — | Due date in YYYY-MM-DD format, or 'clear' to remove |
priority | string | — | |
external_id | string | — | External identifier (e.g. JIRA-123, GH-456) |
wait_for_human | boolean | — | Pause dev agent on this ticket — true holds it for human, false releases (TKR-ADR-0105) |
Parameters from the server's own tool schema.
This tool creates or modifies data (ticket fields) in a reversible manner. Changes to ticket metadata such as status, title, priority, and assignee can be undone or corrected. This does not delete data (Destructive), execute external code (Execute), or move money (Financial). It is a standard Write operation typical of project management systems.
From the tool's definition Tool name is 'update_ticket' and description states it 'Update ticket fields (status, title, content, priority, assignee, scope)' — these are reversible modifications to ticket data.
Risk signalsAccepts raw HTML/template content (content) · High parameter count (10 properties)
Attacks that exploit this kind of access
Update ticket fields (status, title, content, priority, assignee, scope). It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_ticket accepts 10 parameters: scope, title, number, status, content, assignee, due_date, priority, external_id, wait_for_human. Required: number. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr 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 Tickr. 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 Tickr MCP server (@k-system/tickr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →