assign_cycle · Tickr MCP: Risk & Policy

WHAT IT DOES

What assign_cycle does on Tickr

AI agents use assign_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.

PARAMETERS

Parameter	Type	Required	Description
`number`	string	Yes	Ticket display number, e.g. 'TKR-42' (legacy) or 'TKR-BUG-0042' (typed)
`project`	string	Yes	Project slug
`cycle_id`	string	Yes	UUID of the cycle

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why assign_cycle needs a policy

This tool modifies ticket metadata by assigning it to a sprint/cycle. The operation is reversible (a ticket can be reassigned to a different cycle or unassigned), so it falls under Write rather than Destructive. The blast radius is medium because incorrect cycle assignments could disrupt sprint planning and team coordination, but the change can be easily undone.

From the tool's definition Tool name 'assign_cycle' and description 'Assign a ticket to a cycle (sprint)' indicate a create or modify operation that updates a ticket's cycle assignment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_cycle Rate-limited

assign_cycle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "assign_cycle": {
      "limits": [
        {
          "counter": "assign_cycle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tickr, so you can run agents against it safely.

FAQ

Questions about assign_cycle

What does the assign_cycle tool do? +

Assign a ticket to a cycle (sprint). 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.

What parameters does assign_cycle accept? +

assign_cycle accepts 3 parameters: number, project, cycle_id. Required: number, project, cycle_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on assign_cycle? +

Register the Tickr MCP server in PolicyLayer and add a rule for assign_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.

What risk level is assign_cycle? +

assign_cycle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit assign_cycle? +

Yes. Add a rate_limit block to the assign_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.

How do I block assign_cycle completely? +

Set action: deny in the PolicyLayer policy for assign_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.

What MCP server provides assign_cycle? +

assign_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.