run_saved_config · Artillery MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_saved_config does on Artillery MCP Server

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

This tool runs code/external operations (load testing framework) whose behavioral impact depends on configuration parameters. While not directly destructive or financial, executing load tests against systems without authorization could disrupt services, cause DoS, or consume significant resources.

From the tool's definition Tool 'run_saved_config' executes Artillery load tests using a saved configuration. The server description states it 'Enables running and inspecting Artillery load tests' and this tool triggers test execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_saved_config Rate-limited

run_saved_config 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_saved_config": {
      "limits": [
        {
          "counter": "run_saved_config_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_saved_config

What does the run_saved_config tool do? +

Run an Artillery test using a previously saved 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.

How do I enforce a policy on run_saved_config? +

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

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

Can I rate-limit run_saved_config? +

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

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

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