zendesk_search
Search Zendesk with the query DSL (e.g. 'type:ticket status:open priority:urgent').
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/zendesk-search.md
What zendesk_search does on UnClick
AI agents call zendesk_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Agent email address |
query | string | Yes | Zendesk search query |
api_token | string | Yes | Zendesk API token |
subdomain | string | Yes | Zendesk subdomain (e.g. mycompany) |
Parameters from the server's own tool schema.
Why zendesk_search is rated Low
This tool performs a search operation, which is a read-only query against Zendesk. It uses a query DSL to filter and retrieve tickets and related data but does not create, modify, delete, or execute external operations. The severity is low because search queries have minimal blast radius—they retrieve information without side effects, though information disclosure itself is a consideration in a multi-tenant system.
From the tool's definition Tool name 'zendesk_search' and description 'Search Zendesk with the query DSL' indicate retrieval of existing data from Zendesk without modification or deletion.
Attacks that exploit this kind of access
The rule that runs zendesk_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zendesk_search, this is the rule to start with:
zendesk_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every zendesk_search call is checked against it from then on.
Questions about zendesk_search
Search Zendesk with the query DSL (e.g. 'type:ticket status:open priority:urgent'). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
zendesk_search accepts 4 parameters: email, query, api_token, subdomain. Required: email, query, api_token, subdomain. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for zendesk_search: 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 UnClick. Nothing to install.
zendesk_search 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 zendesk_search 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 zendesk_search. 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.
zendesk_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue