Run a preset test type (smoke, baseline, soak, spike) with minimal configuration.
AI agents invoke run_preset_test 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.
This tool executes load tests (smoke, baseline, soak, spike) which are external operations with non-trivial side effects. While load tests are designed to be safe and reversible (unlike destructive operations), they can impact system performance, generate infrastructure costs, consume resources, and potentially interfere with other services or users.
From the tool's definition Tool description states 'Run a preset test type' which directly executes an external operation (load testing).
Attacks that exploit this kind of access
Run a preset test type (smoke, baseline, soak, spike) with minimal configuration. 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.
Register the Artillery MCP Server MCP server in PolicyLayer and add a rule for run_preset_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 Artillery MCP Server. Nothing to install.
run_preset_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 run_preset_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 run_preset_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.
run_preset_test 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.
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 →