AI agents use create_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 | Yes | Cycle name |
endDate | string | Yes | End date (ISO 8601, e.g. '2026-03-29') |
project | string | Yes | Project slug |
startDate | string | Yes | Start date (ISO 8601, e.g. '2026-03-15') |
Parameters from the server's own tool schema.
This tool creates a new project management entity (a sprint/cycle) which is reversible—cycles can typically be deleted, archived, or modified in project management systems. This is a Write operation with medium severity because misuse could create unwanted sprints affecting project planning, but the blast radius is limited to project metadata and does not involve financial transactions or irreversible destruction.
From the tool's definition Tool name 'create_cycle' and description 'Create a new cycle (sprint) in a project' indicate data creation with no irreversible deletion or financial impact.
Attacks that exploit this kind of access
Create a new 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.
create_cycle accepts 4 parameters: name, endDate, project, startDate. Required: name, endDate, project, startDate. 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_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.
create_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 create_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 create_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.
create_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 →