List tickets, newest first. Paginated. Optional filters by department/status/assignee.
AI agents call zoho_desk_list_tickets to retrieve information from Vibing Steampunk (vsp) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries ticket data from Zoho Desk without side effects. Filtering and listing are read-only operations. The blast radius of misuse is minimal—an agent could retrieve sensitive ticket information but cannot modify, delete, or trigger external actions. Classified as Read with low severity.
From the tool's definition Tool name contains 'list' and description states 'List tickets' with optional filters. No modification, deletion, or execution capabilities mentioned. Returns paginated ticket data.
Attacks that exploit this kind of access
List tickets, newest first. Paginated. Optional filters by department/status/assignee. It is categorised as a Read tool in the Vibing Steampunk (vsp) MCP Server, which means it retrieves data without modifying state.
Register the Vibing Steampunk (vsp) MCP server in PolicyLayer and add a rule for zoho_desk_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 Vibing Steampunk (vsp). Nothing to install.
zoho_desk_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 zoho_desk_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 zoho_desk_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.
zoho_desk_list_tickets is provided by the Vibing Steampunk (vsp) MCP server (sangvucitek/mcp_sap). 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 →