AI agents call list_cycles to retrieve information from Tickr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Project slug |
Parameters from the server's own tool schema.
This tool retrieves or queries information about cycles (sprints) in a project management context. There are no modifications, deletions, or external operations triggered. This is a standard read operation typical of project management systems.
From the tool's definition Tool name is 'list_cycles' with description 'List cycles (sprints) for a project' — the word 'List' and verb 'list' indicate retrieval of data with no side effects.
Attacks that exploit this kind of access
List cycles (sprints) for a project. It is categorised as a Read tool in the Tickr MCP Server, which means it retrieves data without modifying state.
list_cycles accepts 1 parameter: project. Required: 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 list_cycles: 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.
list_cycles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_cycles 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 list_cycles. 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.
list_cycles 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 →