Search Zendesk tickets using query syntax. Supports text search, filters, custom fields, and date ranges.
AI agents call search_tickets to retrieve information from Zendesk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search/query operation that retrieves ticket data without side effects. It does not create, modify, delete, or execute external operations. This is a classic Read operation retrieving information from the Zendesk system.
From the tool's definition Tool description explicitly states 'Search Zendesk tickets' with support for 'text search, filters, custom fields, and date ranges' — these are all retrieval and query operations with no mention of modification or deletion capabilities.
Attacks that exploit this kind of access
Search Zendesk tickets using query syntax. Supports text search, filters, custom fields, and date ranges. It is categorised as a Read tool in the Zendesk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zendesk MCP Server MCP server in PolicyLayer and add a rule for 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 Zendesk MCP Server. Nothing to install.
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 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 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.
search_tickets is provided by the Zendesk MCP Server MCP server (kdopenshaw/zendesk-mcp-server). 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 →