wizard_start · Artillery MCP Server MCP: Risk & Policy

WHAT IT DOES

What wizard_start does on Artillery MCP Server

AI agents invoke wizard_start to trigger actions in Artillery MCP Server. 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 IT NEEDS A POLICY

Why wizard_start needs a policy

This tool triggers an interactive wizard that builds and configures load tests. Load testing involves executing network requests and operations against target systems, making it an Execute-category tool. The severity is medium rather than high because the wizard is exploratory/interactive (lower immediate blast radius), but misuse could generate and run tests against unintended targets.

From the tool's definition The tool 'wizard_start' initiates an interactive process for 'building Artillery test configurations' which involves programmatic execution and configuration generation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wizard_start Rate-limited

wizard_start 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wizard_start": {
      "limits": [
        {
          "counter": "wizard_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Artillery MCP Server, so you can run agents against it safely.

FAQ

Questions about wizard_start

What does the wizard_start tool do? +

Start a new interactive wizard for building Artillery test configurations. It is categorised as a Execute tool in the Artillery MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wizard_start? +

Register the Artillery MCP Server MCP server in PolicyLayer and add a rule for wizard_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 Artillery MCP Server. Nothing to install.

What risk level is wizard_start? +

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

Can I rate-limit wizard_start? +

Yes. Add a rate_limit block to the wizard_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 wizard_start completely? +

Set action: deny in the PolicyLayer policy for wizard_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 wizard_start? +

wizard_start is provided by the Artillery MCP Server MCP server (jch1887/artillery-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.