AI agents use update_label 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 |
|---|---|---|---|
name | string | — | New label name |
color | string | — | New hex color code, e.g. '#ef4444' |
project | string | Yes | Project slug |
label_id | string | Yes | UUID of the label to update |
Parameters from the server's own tool schema.
Updating a label is a Write operation: it changes project metadata (label properties) in a way that is reversible (the previous label state can be restored by updating again or undoing). It does not execute code, delete data permanently, or move money. The medium severity reflects that misuse could corrupt project organization or confuse team members, but impact is localized to label metadata and easily recoverable.
From the tool's definition Tool is named 'update_label' with description 'Update a label in a project' — this modifies existing label data reversibly within a project management system.
Attacks that exploit this kind of access
Update a label in a project. 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_label accepts 4 parameters: name, color, project, label_id. Required: project, label_id. 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_label: 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_label 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_label 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_label. 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_label 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 →