set_jmeter_property | PolicyLayer

WHAT IT DOES

What set_jmeter_property does on JMeter MCP Server (TypeScript Edition)

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

WHY IT NEEDS A POLICY

Why set_jmeter_property needs a policy

The tool creates or modifies JMeter configuration data in a persistent file (user.properties). While reversible (properties can be changed again), this affects JMeter's runtime behavior and test execution characteristics. The modification could influence test parameters, thread counts, timeouts, or other critical properties that determine how performance tests run.

From the tool's definition Tool name is 'set_jmeter_property' and description states it 'Set a JMeter property in user.properties file'. This modifies configuration state by writing to the user.properties file.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_jmeter_property Rate-limited

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

FAQ

Questions about set_jmeter_property

What does the set_jmeter_property tool do? +

Set a JMeter property in user.properties file. It is categorised as a Write tool in the JMeter MCP Server (TypeScript Edition) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_jmeter_property? +

Register the JMeter MCP Server (TypeScript Edition) MCP server in PolicyLayer and add a rule for set_jmeter_property: 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 set_jmeter_property? +

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

Can I rate-limit set_jmeter_property? +

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

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

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