apply_zendesk_macro
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...
This record as markdown: /tools/freshdesk/apply-zendesk-macro.md
What apply_zendesk_macro does on Freshdesk
AI agents use apply_zendesk_macro to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why apply_zendesk_macro is rated Medium
This tool modifies ticket data through macro application, making it a Write operation rather than Read (it changes state) or Execute (it doesn't run arbitrary code). It's not Destructive because macro applications are typically reversible through subsequent actions.
From the tool's definition The tool description states it 'applies' a Zendesk macro to a ticket, with a mechanism to 'preview' changes first.
Attacks that exploit this kind of access
The rule that runs apply_zendesk_macro 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 apply_zendesk_macro, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every apply_zendesk_macro call is checked against it from then on.
Questions about apply_zendesk_macro
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 Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk 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 Freshdesk. 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 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