AI agents call get_ticket 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' (legacy) or 'TKR-BUG-0042' (typed) |
Parameters from the server's own tool schema.
This tool queries and retrieves ticket information without altering state, creating side effects, or enabling further actions. It is a straightforward read operation typical of project management systems. Severity is low because retrieving ticket details poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_ticket' and description 'Get full ticket detail by display number' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get full ticket detail by display number. It is categorised as a Read tool in the Tickr MCP Server, which means it retrieves data without modifying state.
get_ticket 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_ticket: 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_ticket 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_ticket 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_ticket. 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_ticket 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 →