This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/zendesk-get-ticket.md
What zendesk_get_ticket does on UnClick
AI agents call zendesk_get_ticket 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 |
api_token | string | Yes | Zendesk API token |
subdomain | string | Yes | Zendesk subdomain |
ticket_id | string | Yes | Ticket id |
Parameters from the server's own tool schema.
Why zendesk_get_ticket is rated Low
This is a read-only operation that queries and retrieves a specific ticket from Zendesk. The primary risk is accessing potentially sensitive customer support data (complaints, personal information, billing details) without authorization.
From the tool's definition Tool description states 'Get a single Zendesk ticket' - retrieves ticket data by ID with no modification or deletion
Attacks that exploit this kind of access
The rule that runs zendesk_get_ticket 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_get_ticket, this is the rule to start with:
zendesk_get_ticket 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_get_ticket call is checked against it from then on.
Questions about zendesk_get_ticket
Get a single Zendesk ticket by id. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
zendesk_get_ticket accepts 4 parameters: email, api_token, subdomain, ticket_id. Required: email, api_token, subdomain, ticket_id. 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_get_ticket: 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_get_ticket 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_get_ticket 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_get_ticket. 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_get_ticket 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