send_sequence_test_email
Queue a real test send for one saved action_email step in a sequence. Call get_sequence first and pass the target sequence.emails entry
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/send-sequence-test-email.md
What send_sequence_test_email does on Sequenzy Mcp
AI agents invoke send_sequence_test_email to trigger actions in Sequenzy Mcp. 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.
Why send_sequence_test_email is rated High
Triggers an actual email send operation, an external action with real-world effects.
From the tool's definition Queue a real test send for one saved action_email step
Attacks that exploit this kind of access
The rule that runs send_sequence_test_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_sequence_test_email, this is the rule to start with:
send_sequence_test_email 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every send_sequence_test_email call is checked against it from then on.
Questions about send_sequence_test_email
Queue a real test send for one saved action_email step in a sequence. Call get_sequence first and pass the target sequence.emails entry. It is categorised as a Execute tool in the Sequenzy Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sequenzy MCP server in PolicyLayer and add a rule for send_sequence_test_email: 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 Sequenzy Mcp. Nothing to install.
send_sequence_test_email 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 send_sequence_test_email 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_sequence_test_email. 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_sequence_test_email is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
Across the catalogue