Review tickets in Sanka. Use this when the user wants to inspect support or service tickets in the current workspace.
AI agents call list_tickets 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 performs a read-only operation that retrieves and displays ticket information from the system. There is no indication it modifies, deletes, executes code, or involves financial transactions. The verb 'review' and 'inspect' confirm passive data retrieval. The blast radius of misuse is minimal — an attacker could see sensitive ticket content but cannot alter system state.
From the tool's definition Tool name is 'list_tickets' and description states 'Review tickets' and 'inspect support or service tickets' — purely retrieves/queries existing ticket data with no modification or side effects.
Attacks that exploit this kind of access
Review tickets in Sanka. Use this when the user wants to inspect support or service tickets in the current workspace. 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 list_tickets: 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.
list_tickets 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_tickets 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_tickets. 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_tickets 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 →