Batch-fetch multiple Zendesk tickets by their IDs. Fetches up to thousands of tickets in a single call using the Zendesk Show Many API. Automatically batches requests when more than 100 IDs are provided (API limit is 100 per request). Returns all found tickets plus a list of any IDs that were not...
AI agents call get_zendesk_tickets_by_ids 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 ticket data from Zendesk without creating, modifying, deleting, or executing code. It is a simple data query operation with no side effects. The warning about rate limiting with the optional include_comments parameter does not change the fundamental category—it remains a Read operation.
From the tool's definition Tool description states it "Batch-fetch multiple Zendesk tickets by their IDs" and "Fetches up to thousands of tickets in a single call".
Documented attack patterns abuse exactly the kind of access get_zendesk_tickets_by_ids 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 get_zendesk_tickets_by_ids:
{
"version": "1",
"default": "deny",
"tools": {
"get_zendesk_tickets_by_ids": {}
}
}get_zendesk_tickets_by_ids 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.
Batch-fetch multiple Zendesk tickets by their IDs. Fetches up to thousands of tickets in a single call using the Zendesk Show Many API. Automatically batches requests when more than 100 IDs are provided (API limit is 100 per request). Returns all found tickets plus a list of any IDs that were not found. Duplicate and invalid (non-positive) IDs are automatically filtered out. Use include_comments to also fetch comments for each ticket. WARNING: This makes one additional API request per ticket, so avoid using it with large sets (>50 tickets) to prevent rate limiting. Example: Get tickets 101, 102, 103 with their comments: {. 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 get_zendesk_tickets_by_ids: 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.
get_zendesk_tickets_by_ids 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 get_zendesk_tickets_by_ids 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 get_zendesk_tickets_by_ids. 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.
get_zendesk_tickets_by_ids 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.