AI agents call get_next_statuses 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 |
|---|---|---|---|
number | string | Yes | Ticket display number, e.g. 'TKR-42' or 'TKR-BUG-0042' |
Parameters from the server's own tool schema.
This tool reads and returns available workflow transitions for a ticket based on current state and permissions. It has no side effects, creates no data, executes no commands, and performs no destructive or financial operations. It is a pure information retrieval operation typical of project management systems.
From the tool's definition Tool name 'get_next_statuses' and description 'Get available next statuses for a ticket' indicate a query operation that retrieves state information without modifying data.
Attacks that exploit this kind of access
Get available next statuses for a ticket (based on current status and user role). It is categorised as a Read tool in the Tickr MCP Server, which means it retrieves data without modifying state.
get_next_statuses accepts 1 parameter: number. Required: number. 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 get_next_statuses: 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.
get_next_statuses 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 get_next_statuses 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 get_next_statuses. 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.
get_next_statuses 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 →