AI agents invoke execute_jmeter_test_non_gui to trigger actions in JMeter 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.
This tool executes external operations—JMeter test plans—whose effects depend on test configuration and target systems. It is not merely reading or writing data; it actively triggers network requests and performance tests against potentially live infrastructure. This fits the Execute category (runs code/triggers external operations).
From the tool's definition Tool name contains 'execute_jmeter_test' which indicates it runs JMeter performance tests. JMeter executes test plans that can make arbitrary HTTP requests, load tests, and trigger external operations against target systems.
Documented attack patterns abuse exactly the kind of access execute_jmeter_test_non_gui gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JMeter MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_jmeter_test_non_gui:
{
"version": "1",
"default": "deny",
"tools": {
"execute_jmeter_test_non_gui": {
"limits": [
{
"counter": "execute_jmeter_test_non_gui_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_jmeter_test_non_gui 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.
Free to start. No card required.
execute_jmeter_test_non_gui. It is categorised as a Execute tool in the JMeter MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the JMeter MCP Server MCP server in PolicyLayer and add a rule for execute_jmeter_test_non_gui: 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. Nothing to install.
execute_jmeter_test_non_gui is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_jmeter_test_non_gui 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.
Set action: deny in the PolicyLayer policy for execute_jmeter_test_non_gui. 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.
execute_jmeter_test_non_gui is provided by the JMeter MCP Server MCP server (qainsights/jmeter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 JMeter MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 JMeter MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.