quick_test · Artillery MCP Server MCP: Risk & Policy

WHAT IT DOES

What quick_test does on Artillery MCP Server

AI agents invoke quick_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.

WHY IT NEEDS A POLICY

Why quick_test needs a policy

This tool triggers execution of Artillery load tests, which sends real HTTP traffic to target systems. Misuse could cause unintended load/stress on production systems, potential denial-of-service conditions, or unintended charges if targeting cloud services. It falls under Execute as it runs external operations whose effects depend on the arguments provided.

From the tool's definition "Run a quick HTTP test" — actively executes an HTTP load test against a target using Artillery

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quick_test Rate-limited

quick_test 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": {
    "quick_test": {
      "limits": [
        {
          "counter": "quick_test_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 quick_test

What does the quick_test tool do? +

Run a quick HTTP test (if supported by Artillery). 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 quick_test? +

Register the Artillery MCP Server MCP server in PolicyLayer and add a rule for quick_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.

What risk level is quick_test? +

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

Can I rate-limit quick_test? +

Yes. Add a rate_limit block to the quick_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.

How do I block quick_test completely? +

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

What MCP server provides quick_test? +

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

// THE FULL RECORD

quick_test 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 →