AI agents use update_ticket to create or update resources in Pearlog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pearlog environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Ticket ID (required). |
tags | string | — | Comma-separated tags. |
type | string | — | Ticket type. |
status | number | — | Status ID. Use get_status_labels to see available statuses. |
userId | number | — | Assigned user ID. Use list_users to find IDs. |
headline | string | — | Ticket title. |
priority | number | — | Priority: 0=none, 1=low, 2=medium, 3=high. |
planHours | number | — | Estimated hours. |
projectId | number | — | Project ID the ticket belongs to. |
description | string | — | Detailed description. |
dateToFinish | string | — | Due date in YYYY-MM-DD format. |
Parameters from the server's own tool schema.
This tool modifies ticket data but does not delete or destroy records—changes can be undone by updating again. It does not execute arbitrary code, move money, or perform irreversible operations. Write is the appropriate category. Severity is medium because an agent could inadvertently clear important ticket fields or corrupt project data, but the operation remains reversible.
From the tool's definition Tool name 'update_ticket' and description 'Fully update a ticket' indicate data modification. The caveat that 'omitted optional fields may be cleared' shows reversible changes to existing records.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Fully update a ticket. You must supply all fields you want to keep — omitted optional fields may be cleared. Use patch_ticket for partial updates. It is categorised as a Write tool in the Pearlog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_ticket accepts 11 parameters: id, tags, type, status, userId, headline, priority, planHours, projectId, description, dateToFinish. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Pearlog 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 Pearlog. 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 Pearlog MCP server (mcp-server-pearlog). 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 →