add_mixmax_sequence_recipients
Add recipients to a Mixmax sequence, enrolling them in the automated email drip campaign. IMPORTANT: Confirm with the user before calling — this adds real people to a live sequence and they WILL receive emails starting from stage 1. WORKFLOW: 1. list_mixmax_sequences to find the sequence _id 2. O...
This record as markdown: /tools/freshdesk/add-mixmax-sequence-recipients.md
What add_mixmax_sequence_recipients does on Freshdesk
AI agents use add_mixmax_sequence_recipients 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 add_mixmax_sequence_recipients is rated Medium
This tool creates/modifies data by enrolling recipients into an active marketing automation campaign. While it initiates a business operation (sending emails), it is reversible—recipients can be unenrolled and the operation is not destructive or financial in nature.
From the tool's definition Tool description states it will "Add recipients to a Mixmax sequence, enrolling them in the automated email drip campaign" and explicitly warns "this adds real people to a live sequence and they WILL receive emails starting from stage 1."
Attacks that exploit this kind of access
The rule that runs add_mixmax_sequence_recipients 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 add_mixmax_sequence_recipients, this is the rule to start with:
add_mixmax_sequence_recipients 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 add_mixmax_sequence_recipients call is checked against it from then on.
Questions about add_mixmax_sequence_recipients
Add recipients to a Mixmax sequence, enrolling them in the automated email drip campaign. IMPORTANT: Confirm with the user before calling — this adds real people to a live sequence and they WILL receive emails starting from stage 1. WORKFLOW: 1. list_mixmax_sequences to find the sequence _id 2. Optionally get_mixmax_sequence to review the stages/content with the user 3. Confirm recipient list with user 4. Call this tool TEMPLATE VARIABLES: If the sequence stages use variables like {{first_name}}, pass them in the variables object for each recipient. 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 add_mixmax_sequence_recipients: 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.
add_mixmax_sequence_recipients 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 add_mixmax_sequence_recipients 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 add_mixmax_sequence_recipients. 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.
add_mixmax_sequence_recipients 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