Load one ticket from Sanka by ticket id, numeric id, or external reference.
AI agents call get_ticket to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves ticket data without side effects. It fits the Read category as it performs a simple data lookup operation. The low severity reflects minimal blast radius—an AI agent retrieving a ticket causes no damage, data loss, or unintended operations. The high confidence stems from explicit use of 'load' (retrieval language) and absence of any write, execute, delete, or financial keywords.
From the tool's definition Tool name and description indicate retrieval only: 'Load one ticket from Sanka by ticket id, numeric id, or external reference.' Uses the verb 'load' (retrieve) with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Load one ticket from Sanka by ticket id, numeric id, or external reference. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server 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 Sanka MCP Server. 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 Sanka MCP Server MCP server (sankahq/sanka-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 →