zendesk_list_tickets
List recent Zendesk tickets (signals when any are still new).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/zendesk-list-tickets.md
What zendesk_list_tickets does on UnClick
AI agents call zendesk_list_tickets 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 |
limit | number | — | Tickets to return (max 100, default 25) |
sort_by | string | — | Sort field (e.g. created_at, updated_at) |
api_token | string | Yes | Zendesk API token |
subdomain | string | Yes | Zendesk subdomain |
Parameters from the server's own tool schema.
Why zendesk_list_tickets is rated Low
This is fundamentally a Read operation—it retrieves and displays ticket data without creating, modifying, or deleting anything. Severity is medium rather than low because Zendesk tickets typically contain sensitive customer information (PII, account details, support history) that an AI agent could expose or exfiltrate, creating privacy and security risks.
From the tool's definition Tool name contains 'list' and description says 'List recent Zendesk tickets', which is a query/retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs zendesk_list_tickets 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_list_tickets, this is the rule to start with:
zendesk_list_tickets 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_list_tickets call is checked against it from then on.
Questions about zendesk_list_tickets
List recent Zendesk tickets (signals when any are still new). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
zendesk_list_tickets accepts 5 parameters: email, limit, sort_by, api_token, subdomain. Required: email, 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_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 UnClick. Nothing to install.
zendesk_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 zendesk_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 zendesk_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.
zendesk_list_tickets 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