AI agents use create_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 | Yes | Label name |
color | string | Yes | Hex color code, e.g. '#ef4444' |
project | string | Yes | Project slug |
Parameters from the server's own tool schema.
Creating a label is a write operation that adds new metadata to a project. It is reversible (labels can be deleted or modified) and has minimal blast radius—miscreating labels does not corrupt data, delete information, or trigger external operations. This is clearly a Write-category tool with low severity.
From the tool's definition Tool name 'create_label' and description 'Create a new label in a project' indicate data creation. Labels are metadata that can be created and modified reversibly without irreversible consequences.
Attacks that exploit this kind of access
Create a new 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.
create_label accepts 3 parameters: name, color, project. Required: name, color, project. 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 create_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.
create_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 create_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 create_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.
create_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 →