// SCAN REPORT

JMeter MCP Server (TypeScript Edition)

10 tools. 6 can modify or destroy data without limits.

6 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

6 can modify or destroy data

4 read-only

10 tools total

Community server · catalogue entry verified 03/07/2026

How to control JMeter MCP Server (TypeScript Edition) ↓

TOOL MAP

What JMeter MCP Server (TypeScript Edition) exposes to your agents

Read (4) Write / Execute (6) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous JMeter MCP Server (TypeScript Edition) tools

Execute · High execute_distributed_test 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). Execute · High execute_jmeter_test This tool triggers execution of Apache JMeter performance tests, which can generate load against target systems, consume resources, and produce side effects on monitored infrastructure. Execute · High launch_jmeter_gui This tool starts a JMeter GUI instance, which is an external process execution. Write · Medium create_http_test_plan Creating a test plan is a Write operation: it produces new configuration artifacts in the JMeter environment that can be modified or deleted later.

6 of JMeter MCP Server (TypeScript Edition)'s 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control JMeter MCP Server (TypeScript Edition)

PolicyLayer is an MCP gateway — it sits between your AI agents and JMeter MCP Server (TypeScript Edition), and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "create_http_test_plan": {
    "limits": [
      {
        "counter": "create_http_test_plan_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_test_results": {
    "limits": [
      {
        "counter": "analyze_test_results_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register JMeter MCP Server (TypeScript Edition) — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON JMETER MCP SERVER (TYPESCRIPT EDITION) →

Instant setup, no code required.

FULL CATALOGUE

All 10 JMeter MCP Server (TypeScript Edition) tools

EXECUTE 3 tools

Execute execute_distributed_test Execute a distributed test across multiple remote JMeter servers Execute execute_jmeter_test Execute a JMeter test plan in non-GUI mode with comprehensive options Execute launch_jmeter_gui Launch JMeter in GUI mode for test development

WRITE 3 tools

Write create_http_test_plan Create a new HTTP test plan programmatically with customizable options Write generate_html_report Generate an HTML dashboard report from existing JTL results Write set_jmeter_property Set a JMeter property in user.properties file

READ 4 tools

Read analyze_test_results Analyze JMeter test results and provide comprehensive performance metrics, bottleneck identification, and reco Read get_jmeter_properties Get JMeter properties from jmeter.properties file Read list_jmeter_plugins List all installed JMeter plugins Read validate_jmeter Validate that JMeter is installed and accessible, and get version information

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about JMeter MCP Server (TypeScript Edition)

How do I prevent bulk modifications through JMeter MCP Server (TypeScript Edition)? +

The JMeter MCP Server (TypeScript Edition) server has 3 write tools including create_http_test_plan, generate_html_report, set_jmeter_property. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach JMeter MCP Server (TypeScript Edition).

How many tools does the JMeter MCP Server (TypeScript Edition) MCP server expose? +

10 tools across 3 categories: Execute, Read, Write. 4 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on JMeter MCP Server (TypeScript Edition)? +

Register the JMeter MCP Server (TypeScript Edition) MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every JMeter MCP Server (TypeScript Edition) tool call.

Deterministic rules across all 10 JMeter MCP Server (TypeScript Edition) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON JMETER MCP SERVER (TYPESCRIPT EDITION) →

Instant setup, no code required.

10 JMeter MCP Server (TypeScript Edition) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.