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...
AI agents invoke add_mixmax_sequence_recipients to trigger actions in Apple Shortcuts. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — sending automated emails to real people. It is not merely writing data; it initiates a live drip campaign that causes emails to be dispatched to external recipients. The description explicitly warns that recipients 'WILL receive emails,' confirming real-world side effects.
From the tool's definition Add recipients to a Mixmax sequence, enrolling them in the automated email drip campaign... this adds real people to a live sequence and they WILL receive emails starting from stage 1.
Documented attack patterns abuse exactly the kind of access add_mixmax_sequence_recipients 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 add_mixmax_sequence_recipients:
{
"version": "1",
"default": "deny",
"tools": {
"add_mixmax_sequence_recipients": {
"limits": [
{
"counter": "add_mixmax_sequence_recipients_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}add_mixmax_sequence_recipients stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 Execute tool in the Apple Shortcuts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Apple Shortcuts 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 Apple Shortcuts. Nothing to install.
add_mixmax_sequence_recipients is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 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.