perf_loadtest · Yaver MCP: Risk & Policy

WHAT IT DOES

What perf_loadtest does on Yaver

AI agents invoke perf_loadtest to trigger actions in Yaver. 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.

PARAMETERS

Parameter	Type	Required	Description
`url`	string	Yes
`duration`	string	—	Duration (e.g. 30s)
`requests`	integer	—	Total requests (default: 1000)
`concurrency`	integer	—	Concurrent requests (default: 10)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why perf_loadtest needs a policy

perf_loadtest triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

perf_loadtest Rate-limited

perf_loadtest 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": {
    "perf_loadtest": {
      "limits": [
        {
          "counter": "perf_loadtest_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 Yaver, so you can run agents against it safely.

FAQ

Questions about perf_loadtest

What does the perf_loadtest tool do? +

Run a load test on a URL. Returns RPS, latency percentiles, error rate. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does perf_loadtest accept? +

perf_loadtest accepts 4 parameters: url, duration, requests, concurrency. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on perf_loadtest? +

Register the Yaver MCP server in PolicyLayer and add a rule for perf_loadtest: 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 Yaver. Nothing to install.

What risk level is perf_loadtest? +

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

Can I rate-limit perf_loadtest? +

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

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

perf_loadtest is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.