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)...
AI agents call list_zendesk_ticket_fields to retrieve information from Apple Shortcuts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about Zendesk ticket fields (IDs, titles, types, options) for the purpose of discovering field information needed by other operations. It queries and returns data without creating, modifying, deleting, or executing any operations. The tool is explicitly designed as a lookup/discovery mechanism, making it a straightforward Read operation with minimal blast radius if misused.
From the tool's definition Tool name is 'list_zendesk_ticket_fields' with description stating it 'List all ticket fields' and 'Returns field IDs, titles, types, and options.' The verb 'list' and 'returns' indicate read-only data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access list_zendesk_ticket_fields gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for list_zendesk_ticket_fields:
{
"version": "1",
"default": "deny",
"tools": {
"list_zendesk_ticket_fields": {}
}
}list_zendesk_ticket_fields is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 Apple Shortcuts MCP Server, which means it retrieves data without modifying state.
Register the Apple Shortcuts 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 Apple Shortcuts. 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 Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.