execute_distributed_test

WHAT IT DOES

What execute_distributed_test does on JMeter MCP Server (TypeScript Edition)

AI agents invoke execute_distributed_test to trigger actions in JMeter MCP Server (TypeScript Edition). 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 execute_distributed_test needs a policy

This tool triggers execution of performance tests on remote JMeter servers, which qualifies as Execute category—it runs external operations whose effects depend on test parameters (load, duration, targets). The 'distributed' and 'remote servers' aspect amplifies the blast radius: misconfigured tests could overload production systems, cause denial-of-service, exhaust resources, or generate excessive traffic.

From the tool's definition Tool name 'execute_distributed_test' combined with description 'Execute a distributed test across multiple remote JMeter servers' indicates execution of performance tests across remote infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_distributed_test Rate-limited

execute_distributed_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": {
    "execute_distributed_test": {
      "limits": [
        {
          "counter": "execute_distributed_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 JMeter MCP Server (TypeScript Edition), so you can run agents against it safely.

FAQ

Questions about execute_distributed_test

What does the execute_distributed_test tool do? +

Execute a distributed test across multiple remote JMeter servers. It is categorised as a Execute tool in the JMeter MCP Server (TypeScript Edition) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_distributed_test? +

Register the JMeter MCP Server (TypeScript Edition) MCP server in PolicyLayer and add a rule for execute_distributed_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 JMeter MCP Server (TypeScript Edition). Nothing to install.

What risk level is execute_distributed_test? +

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

Can I rate-limit execute_distributed_test? +

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

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

execute_distributed_test is provided by the JMeter MCP Server (TypeScript Edition) MCP server (vjgit-369/jmeter-mcp-server-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.