lexq_ab_test_start

Start an A/B test on a policy group. Requires a challenger version ID and traffic rate.

Server LexQ lexq-io/lexq-cli
Category Execute
Risk class High
Parameters 00 required

What lexq_ab_test_start does on LexQ

AI agents invoke lexq_ab_test_start to trigger actions in LexQ. 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 lexq_ab_test_start needs a policy

Starting an A/B test triggers an external operation that actively routes live traffic to a challenger policy version, affecting real business rule execution. This is not a simple write/create of data — it initiates a running process with real operational impact.

From the tool's definition 'Start an A/B test on a policy group. Requires a challenger version ID and traffic rate.'

Questions about lexq_ab_test_start

What does the lexq_ab_test_start tool do? +

Start an A/B test on a policy group. Requires a challenger version ID and traffic rate. It is categorised as a Execute tool in the LexQ MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lexq_ab_test_start? +

Register the LexQ MCP server in PolicyLayer and add a rule for lexq_ab_test_start: 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 LexQ. Nothing to install.

What risk level is lexq_ab_test_start? +

lexq_ab_test_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lexq_ab_test_start? +

Yes. Add a rate_limit block to the lexq_ab_test_start 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.

How do I block lexq_ab_test_start completely? +

Set action: deny in the PolicyLayer policy for lexq_ab_test_start. 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.

What MCP server provides lexq_ab_test_start? +

lexq_ab_test_start is provided by the LexQ MCP server (lexq-io/lexq-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.