update_ab_test
Update A/B test settings. Campaign tests use testPercentage, testDurationMinutes, and winnerCriteria. Sequence tests use testType, winnerThreshold, and winnerCriteria; changing live or already-used sequence settings requires confirmLiveChange. Provide at least one setting.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/update-ab-test.md
What update_ab_test does on Sequenzy Mcp
AI agents use update_ab_test to create or update resources in Sequenzy Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sequenzy Mcp environment.
Why update_ab_test is rated Medium
This tool modifies A/B test configurations for campaigns and sequences within an email marketing system. The Update operation makes it Write-category (reversible modification of data). Severity is medium because misuse could disrupt active marketing campaigns or redirect campaign winners based on incorrect criteria, but changes are reversible and don't cause financial loss, data deletion, or arbitrary code execution.
From the tool's definition Tool description states 'Update A/B test settings' with parameters like testPercentage, testDurationMinutes, winnerCriteria, testType, and winnerThreshold.
Attacks that exploit this kind of access
The rule that runs update_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 update_ab_test, this is the rule to start with:
update_ab_test stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 update_ab_test call is checked against it from then on.
Questions about update_ab_test
Update A/B test settings. Campaign tests use testPercentage, testDurationMinutes, and winnerCriteria. Sequence tests use testType, winnerThreshold, and winnerCriteria; changing live or already-used sequence settings requires confirmLiveChange. Provide at least one setting. It is categorised as a Write tool in the Sequenzy Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sequenzy MCP server in PolicyLayer and add a rule for update_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.
update_ab_test is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
This server
Across the catalogue