create_http_test_plan

WHAT IT DOES

What create_http_test_plan does on JMeter MCP Server (TypeScript Edition)

AI agents use create_http_test_plan 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 create_http_test_plan needs a policy

Creating a test plan is a Write operation: it produces new configuration artifacts in the JMeter environment that can be modified or deleted later. While the server can execute tests (Execute category tools exist separately), this tool itself only creates test definitions, not execute them.

From the tool's definition Tool description states 'Create a new HTTP test plan programmatically' — creates new test configuration data that is stored and reusable, with reversible modifications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_http_test_plan Rate-limited

create_http_test_plan 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": {
    "create_http_test_plan": {
      "limits": [
        {
          "counter": "create_http_test_plan_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 create_http_test_plan

What does the create_http_test_plan tool do? +

Create a new HTTP test plan programmatically with customizable options. 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 create_http_test_plan? +

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

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

Can I rate-limit create_http_test_plan? +

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

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

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