AI agents call list_ticket_fields to retrieve information from Zendesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about the structure of ticket fields (names, types, options) in Zendesk. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It is a straightforward data retrieval operation, making it clearly a Read category tool with low severity risk.
From the tool's definition Tool name is 'list_ticket_fields' and description states 'List all ticket fields' — a read-only operation that retrieves metadata about ticket field definitions without modifying or deleting data.
Attacks that exploit this kind of access
List all ticket fields including custom fields with their types and options. It is categorised as a Read tool in the Zendesk MCP Server, which means it retrieves data without modifying state.
Register the Zendesk MCP server in PolicyLayer and add a rule for list_ticket_fields: 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. Nothing to install.
list_ticket_fields 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 list_ticket_fields 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 list_ticket_fields. 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.
list_ticket_fields is provided by the Zendesk MCP server (kalchevs/zendesk-mcp). 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 →