run_test_from_file · Artillery MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_test_from_file does on Artillery MCP Server

AI agents invoke run_test_from_file 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 run_test_from_file needs a policy

This tool triggers external operations (load tests against target systems) whose effects cannot be predicted or contained without inspecting the config file contents. An AI agent with access to arbitrary config files could inadvertently or maliciously launch load tests against unintended targets, causing service degradation or denial-of-service conditions.

From the tool's definition Tool runs an Artillery test from a config file—'run_test_from_file' executes a load testing operation whose side effects (network traffic, resource consumption, potential service disruption) depend on the test configuration and target specified in the file.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_test_from_file Rate-limited

run_test_from_file 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": {
    "run_test_from_file": {
      "limits": [
        {
          "counter": "run_test_from_file_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 run_test_from_file

What does the run_test_from_file tool do? +

Run an Artillery test from a config file path. 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 run_test_from_file? +

Register the Artillery MCP Server MCP server in PolicyLayer and add a rule for run_test_from_file: 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 run_test_from_file? +

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

Can I rate-limit run_test_from_file? +

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

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

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