Run an Artillery test from inline configuration text.
AI agents invoke run_test_inline 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 against specified targets based on user-provided configuration. While not destructive to the user's own data, it triggers external operations (network requests to target systems) whose effects depend on the provided arguments (target URL, request patterns, etc.). This could be misused to perform unauthorized load testing or DDoS-like attacks against systems.
From the tool's definition Tool name 'run_test_inline' and description 'Run an Artillery test from inline configuration text' indicates execution of load testing operations. Artillery is a tool that performs HTTP requests and other network operations against target systems.
Attacks that exploit this kind of access
Run an Artillery test from inline configuration text. 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_test_inline: 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_test_inline 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_test_inline 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_test_inline. 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_test_inline 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.
run_test_inline is one line of Artillery MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →