restart_ab_test
Run another sequence A/B test after a winner is selected. By default the winner becomes the new control; pass sourceVariantId to use another variant as the control email.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/restart-ab-test.md
What restart_ab_test does on Sequenzy Mcp
AI agents invoke restart_ab_test 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 restart_ab_test is rated High
This tool executes a business operation (A/B test restart) with conditional logic based on the sourceVariantId parameter. While it modifies email marketing behavior, it is not Destructive (tests are reversible), not Financial (no money moves), and not Write (it doesn't simply create/modify data—it runs/orchestrates a process).
From the tool's definition Tool description states 'Run another sequence A/B test' — the verb 'Run' indicates execution of a process/operation. The tool triggers a test workflow that modifies campaign behavior (selecting winners, reassigning control variants).
Attacks that exploit this kind of access
The rule that runs restart_ab_test 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 restart_ab_test, this is the rule to start with:
restart_ab_test 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 restart_ab_test call is checked against it from then on.
Questions about restart_ab_test
Run another sequence A/B test after a winner is selected. By default the winner becomes the new control; pass sourceVariantId to use another variant as the control email. 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 restart_ab_test: 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.
restart_ab_test 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 restart_ab_test 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 restart_ab_test. 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.
restart_ab_test 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