AI agents use update_cycle 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 cycle name |
status | string | — | New status: planned, active, completed |
endDate | string | — | New end date (ISO 8601, e.g. '2026-03-29') |
project | string | Yes | Project slug |
cycle_id | string | Yes | UUID of the cycle to update |
startDate | string | — | New start date (ISO 8601, e.g. '2026-03-15') |
Parameters from the server's own tool schema.
This tool modifies existing sprint/cycle data within a project management system. The change is reversible—cycles can be updated again with different values. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium: incorrect cycle updates could disrupt sprint planning and team coordination, but the change can be corrected.
From the tool's definition Tool name 'update_cycle' and description 'Update a cycle (sprint) in a project' indicate modification of project management data. The term 'update' confirms reversible data modification rather than deletion or irreversible changes.
Attacks that exploit this kind of access
Update a cycle (sprint) 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_cycle accepts 6 parameters: name, status, endDate, project, cycle_id, startDate. Required: project, cycle_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_cycle: 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_cycle 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_cycle 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_cycle. 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_cycle 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 →