update_transitions · Tickr MCP: Risk & Policy

WHAT IT DOES

What update_transitions does on Tickr

AI agents use update_transitions 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
`project`	string	Yes	Project slug
`transitions`	array	Yes	Array of transition definitions

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_transitions needs a policy

This tool modifies workflow transition rules for a project, which is a Write operation (creates or modifies data reversibly). The severity is high because replacing all transitions could disrupt project workflows and affect all team members' ability to progress tickets through states.

From the tool's definition Tool name 'update_transitions' and description 'Replace all workflow transitions for a project' indicate modification of project configuration. The word 'Replace' shows this is reversible data modification, not deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_transitions Rate-limited

update_transitions 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": {
    "update_transitions": {
      "limits": [
        {
          "counter": "update_transitions_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 update_transitions

What does the update_transitions tool do? +

Replace all workflow transitions for 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.

What parameters does update_transitions accept? +

update_transitions accepts 2 parameters: project, transitions. Required: project, transitions. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_transitions? +

Register the Tickr MCP server in PolicyLayer and add a rule for update_transitions: 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 update_transitions? +

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

Can I rate-limit update_transitions? +

Yes. Add a rate_limit block to the update_transitions 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 update_transitions completely? +

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

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