list_mixmax_sequences
List Mixmax sequences (automated email drip campaigns). Returns for each sequence: - _id: Use with get_mixmax_sequence for full details or add_mixmax_sequence_recipients to enroll people - name: Sequence name - numStages: Number of email stages in the drip - isPaused: Whether the sequence is curr...
This record as markdown: /tools/freshdesk/list-mixmax-sequences.md
What list_mixmax_sequences does on Freshdesk
AI agents call list_mixmax_sequences to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_mixmax_sequences is rated Low
This tool retrieves or queries data about email drip campaigns without side effects. It is designed for discovery and inspection of sequences, not creation, modification, deletion, or execution. The returned data enables downstream actions (like add_mixmax_sequence_recipients), but the tool itself only performs a read operation.
From the tool's definition Tool description states 'List Mixmax sequences' and returns metadata about automated email campaigns including _id, name, numStages, isPaused, and recipient statistics.
Attacks that exploit this kind of access
The rule that runs list_mixmax_sequences 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 list_mixmax_sequences, this is the rule to start with:
list_mixmax_sequences is read-only, so it stays allowed. 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 list_mixmax_sequences call is checked against it from then on.
Questions about list_mixmax_sequences
List Mixmax sequences (automated email drip campaigns). Returns for each sequence: - _id: Use with get_mixmax_sequence for full details or add_mixmax_sequence_recipients to enroll people - name: Sequence name - numStages: Number of email stages in the drip - isPaused: Whether the sequence is currently active - numRecipients / numFinished / numBounced: Recipient stats TYPICAL WORKFLOW: 1. list_mixmax_sequences to find the sequence 2. get_mixmax_sequence with the _id to see stages/content 3. add_mixmax_sequence_recipients to enroll contacts PAGINATION: Cursor-based. If hasNext is true, pass the. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for list_mixmax_sequences: 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.
list_mixmax_sequences is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_mixmax_sequences 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 list_mixmax_sequences. 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.
list_mixmax_sequences 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