AI agents use patch_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 | — | New comma-separated tags. |
type | string | — | New ticket type. |
status | number | — | New status ID (moves ticket to a different kanban column). Use get_status_labels to see options. |
userId | number | — | Assign to this user ID. Use list_users to find IDs. Set to 0 to unassign. |
headline | string | — | New ticket title. |
priority | number | — | New priority: 0=none, 1=low, 2=medium, 3=high. |
planHours | number | — | New estimated hours. |
description | string | — | New description. |
dateToFinish | string | — | New due date in YYYY-MM-DD format. |
Parameters from the server's own tool schema.
The tool modifies ticket properties in a controlled, non-destructive manner. While the sibling delete_ticket is Destructive, patch_ticket only performs partial updates that can be undone (e.g., status can be changed back, reassignments reversed, priority adjusted again). This is a classic Write operation.
From the tool's definition Tool description states 'Partially update a ticket' and explicitly mentions changing status, reassigning, and updating priority — all reversible modifications to existing data.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Partially update a ticket — only the fields you provide are changed. Ideal for changing status, reassigning, updating priority, etc. 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.
patch_ticket accepts 10 parameters: id, tags, type, status, userId, headline, priority, planHours, 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 patch_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.
patch_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 patch_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 patch_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.
patch_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 →