AI agents call list_transitions 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 is a read-only operation that retrieves and displays workflow transition information for informational purposes. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial operations. The blast radius of misuse is minimal—an attacker could only gain visibility into workflow configurations.
From the tool's definition Tool name 'list_transitions' and description 'List workflow transitions for a project' indicate a retrieval operation that queries existing workflow state data without modifying or executing external actions.
Attacks that exploit this kind of access
List workflow transitions for a project. It is categorised as a Read tool in the Tickr MCP Server, which means it retrieves data without modifying state.
list_transitions 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_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.
list_transitions 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_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.
Set action: deny in the PolicyLayer policy for list_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.
list_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.
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 →