Preview and apply a Zendesk macro to a ticket. First previews what changes the macro would make, then applies them. Set preview_only=true to see the changes without applying. This tool makes 2 API calls: one to preview, one to apply. The preview shows the resulting ticket state after macro applic...
AI agents use apply_zendesk_macro to create or update resources in Apple Shortcuts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Shortcuts environment.
This tool creates or modifies ticket data in Zendesk by applying a macro, which is a reversible Write operation. While it could potentially have side effects depending on macro configuration (e.g., sending notifications), the primary function is data modification of the ticket itself.
From the tool's definition The tool description explicitly states it 'apply[s]' a Zendesk macro to a ticket, which modifies ticket state. The description notes 'This tool makes 2 API calls: one to preview, one to apply' and 'When applied, the macro' [modifies the ticket].
Documented attack patterns abuse exactly the kind of access apply_zendesk_macro 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 apply_zendesk_macro:
{
"version": "1",
"default": "deny",
"tools": {
"apply_zendesk_macro": {
"limits": [
{
"counter": "apply_zendesk_macro_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}apply_zendesk_macro stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Preview and apply a Zendesk macro to a ticket. First previews what changes the macro would make, then applies them. Set preview_only=true to see the changes without applying. This tool makes 2 API calls: one to preview, one to apply. The preview shows the resulting ticket state after macro application. When applied, the macro. It is categorised as a Write tool in the Apple Shortcuts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for apply_zendesk_macro: 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.
apply_zendesk_macro is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the apply_zendesk_macro 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 apply_zendesk_macro. 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.
apply_zendesk_macro 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.