AI agents use create_status 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 | Status display name |
slug | string | Yes | Status slug (URL-safe identifier) |
color | string | Yes | Hex color code, e.g. '#3b82f6' |
emoji | string | — | Emoji icon for the status |
project | string | Yes | Project slug |
category | string | Yes | Category: backlog, active, done, cancelled |
isDefault | boolean | — | Whether this is the default status for new tickets |
sortOrder | number | Yes | Sort order (0-based) |
isTerminal | boolean | — | Whether this is a terminal (closed) status |
Parameters from the server's own tool schema.
This tool creates (writes) a new workflow status, a reversible change to project configuration. It does not delete, execute arbitrary code, or move money. The blast radius is medium because misconfiguration of workflow statuses could disrupt team processes, but the action itself is reversible via update or deletion of the created status.
From the tool's definition Tool name is 'create_status' and description states 'Create a new workflow status in a project' — this creates a new configuration object that modifies project workflow state.
Attacks that exploit this kind of access
Create a new workflow status 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_status accepts 9 parameters: name, slug, color, emoji, project, category, isDefault, sortOrder, isTerminal. Required: name, slug, color, project, category, sortOrder. 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_status: 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_status 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_status 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_status. 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_status 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 →