Search tickets. Supports keyword (_all) plus structured filters.
AI agents call zoho_desk_search_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 or queries ticket data based on search criteria without creating, modifying, or deleting records. It is a pure read operation with minimal blast radius if misused by an AI agent—the worst outcome would be exposure of ticket information already accessible within the system. No financial, destructive, or executable side effects are possible.
From the tool's definition Tool name 'zoho_desk_search_tickets' and description 'Search tickets. Supports keyword (_all) plus structured filters.' indicate a query/search operation with no modification or deletion of data.
Attacks that exploit this kind of access
Search tickets. Supports keyword (_all) plus structured filters. 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_search_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_search_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_search_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_search_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_search_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 →