list_zendesk_ticket_fields
List all ticket fields including custom fields. Returns field IDs, titles, types, and options. Essential for: - Finding custom field IDs for create/update operations - Discovering dropdown options for custom fields - Understanding required fields Custom fields use numeric IDs (e.g., 360001234567)...
This record as markdown: /tools/freshdesk/list-zendesk-ticket-fields.md
What list_zendesk_ticket_fields does on Freshdesk
AI agents call list_zendesk_ticket_fields to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_zendesk_ticket_fields is rated Low
This is a query/list operation that retrieves metadata about Zendesk ticket field configurations. It has no side effects—no data is created, modified, or deleted. The tool serves an informational purpose to help identify field structures for other operations. The low severity reflects minimal blast radius if misused by an agent; it merely exposes field naming and structure information.
From the tool's definition Tool description explicitly states 'List all ticket fields' and 'discovering' information. The function retrieves and returns metadata (field IDs, titles, types, options) without modifying any data.
Attacks that exploit this kind of access
The rule that runs list_zendesk_ticket_fields safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_zendesk_ticket_fields, this is the rule to start with:
list_zendesk_ticket_fields 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 Freshdesk, apply this rule, and every list_zendesk_ticket_fields call is checked against it from then on.
Questions about list_zendesk_ticket_fields
List all ticket fields including custom fields. Returns field IDs, titles, types, and options. Essential for: - Finding custom field IDs for create/update operations - Discovering dropdown options for custom fields - Understanding required fields Custom fields use numeric IDs (e.g., 360001234567) not names. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for list_zendesk_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 Freshdesk. Nothing to install.
list_zendesk_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_zendesk_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_zendesk_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_zendesk_ticket_fields is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue