save_config · Artillery MCP Server MCP: Risk & Policy

WHAT IT DOES

What save_config does on Artillery MCP Server

AI agents use save_config to create or update resources in Artillery MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Artillery MCP Server environment.

WHY IT NEEDS A POLICY

Why save_config needs a policy

This tool creates or updates Artillery configuration files, which is a write operation. It is reversible (configs can be edited or deleted separately) and has no immediate destructive, financial, or code execution effects. Severity is medium because misconfigured test parameters could lead to resource exhaustion or unintended load against production systems, but the tool itself merely persists configuration data.

From the tool's definition Tool description explicitly states 'Save a new Artillery configuration or update an existing one' — a reversible write operation that creates or modifies data without executing tests or deleting resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_config Rate-limited

save_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_config": {
      "limits": [
        {
          "counter": "save_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 save_config

What does the save_config tool do? +

Save a new Artillery configuration or update an existing one. It is categorised as a Write tool in the Artillery MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_config? +

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

save_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_config? +

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

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

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