AI agents use update_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 | — | New display name |
color | string | — | New hex color code, e.g. '#3b82f6' |
emoji | string | — | New emoji icon |
project | string | Yes | Project slug |
category | string | — | New category: backlog, active, done, cancelled |
status_id | string | Yes | Status ID to update |
Parameters from the server's own tool schema.
The tool updates workflow status, which is a modification of existing data. This is reversible (status can be changed again) and has no financial impact, so it falls under Write rather than Destructive or Financial. The severity is medium because incorrect status updates could impact project tracking and team coordination, but the change can be undone.
From the tool's definition Tool description states "Update a workflow status in a project" — this modifies project state by changing ticket or workflow status, which is a reversible write operation typical of project management tools.
Attacks that exploit this kind of access
Update a 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.
update_status accepts 6 parameters: name, color, emoji, project, category, status_id. Required: project, status_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_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.
update_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 update_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 update_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.
update_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 →