send_mixmax_snippet
Send a Mixmax template (snippet) to one or more recipients. IMPORTANT: Confirm with the user before sending — this sends a real email using the template content. WORKFLOW: 1. list_mixmax_snippets to find the template and its _id 2. Check the snippet body for template variables (e.g. {{first_name}...
This record as markdown: /tools/freshdesk/send-mixmax-snippet.md
What send_mixmax_snippet does on Freshdesk
AI agents use send_mixmax_snippet 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 send_mixmax_snippet is rated Medium
This tool creates (sends) email messages, which is a reversible write operation. While emails cannot be technically unsent after delivery, they are not destructively overwriting or deleting data.
From the tool's definition Tool description states it "Send[s] a Mixmax template (snippet) to one or more recipients" and explicitly notes "this sends a real email". The workflow confirms it dispatches email communications with template content to specified recipients.
Attacks that exploit this kind of access
The rule that runs send_mixmax_snippet 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 send_mixmax_snippet, this is the rule to start with:
send_mixmax_snippet 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 send_mixmax_snippet call is checked against it from then on.
Questions about send_mixmax_snippet
Send a Mixmax template (snippet) to one or more recipients. IMPORTANT: Confirm with the user before sending — this sends a real email using the template content. WORKFLOW: 1. list_mixmax_snippets to find the template and its _id 2. Check the snippet body for template variables (e.g. {{first_name}}, {{company}}) 3. Confirm recipients and variable values with user 4. Call this tool with matching variables NOTE: Variables are applied to ALL recipients equally. If you need different variables per recipient, send one at a time. 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 send_mixmax_snippet: 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.
send_mixmax_snippet 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 send_mixmax_snippet 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 send_mixmax_snippet. 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.
send_mixmax_snippet 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