get_mixmax_sequence
Get full details for a single Mixmax sequence including all stages. Returns: - name, isPaused, createdAt - stages: Array of email steps, each with subject line, body content, delay settings, and send window - Recipient statistics (total, finished, bounced, paused) - Scheduling rules (send window,...
This record as markdown: /tools/freshdesk/get-mixmax-sequence.md
What get_mixmax_sequence does on Freshdesk
AI agents call get_mixmax_sequence 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 get_mixmax_sequence is rated Low
This tool queries and retrieves configuration and statistics about an email sequence without side effects. It is purely informational—reading existing data about email stages, recipient counts, and scheduling settings. The note to 'USE list_mixmax_sequences FIRST to find the _id' confirms it is a lookup/fetch operation. No data is created, modified, or deleted, and no external actions are triggered.
From the tool's definition Tool retrieves full details for a single Mixmax sequence and returns name, stages, recipient statistics, and scheduling rules. The description uses retrieval language: 'Get full details', 'Returns' data. No modification, deletion, or execution occurs.
Attacks that exploit this kind of access
The rule that runs get_mixmax_sequence 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 get_mixmax_sequence, this is the rule to start with:
get_mixmax_sequence 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 get_mixmax_sequence call is checked against it from then on.
Questions about get_mixmax_sequence
Get full details for a single Mixmax sequence including all stages. Returns: - name, isPaused, createdAt - stages: Array of email steps, each with subject line, body content, delay settings, and send window - Recipient statistics (total, finished, bounced, paused) - Scheduling rules (send window, timezone, skip weekends) USE list_mixmax_sequences FIRST to find the _id. 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 get_mixmax_sequence: 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.
get_mixmax_sequence 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 get_mixmax_sequence 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 get_mixmax_sequence. 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.
get_mixmax_sequence 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