webtool_performance_test · Webtools MCP Server MCP

WHAT IT DOES

What webtool_performance_test does on Webtools MCP Server

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

WHY IT NEEDS A POLICY

Why webtool_performance_test needs a policy

The tool executes performance testing operations across multiple contexts (devices, network conditions), which constitutes active execution of code/operations rather than passive data retrieval. While not destructive or financial, it triggers external operations with real-world effects (network simulation, device emulation, resource consumption).

From the tool's definition Tool performs 'Run performance tests across different devices and network conditions' — this actively executes test operations and triggers external browser/device actions whose side effects depend on input parameters (device type, network profile, test…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

webtool_performance_test Rate-limited

webtool_performance_test 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": {
    "webtool_performance_test": {
      "limits": [
        {
          "counter": "webtool_performance_test_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 Webtools MCP Server, so you can run agents against it safely.

FAQ

Questions about webtool_performance_test

What does the webtool_performance_test tool do? +

Run performance tests across different devices and network conditions. Compare results and identify device-specific or network-specific issues. It is categorised as a Execute tool in the Webtools MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on webtool_performance_test? +

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

What risk level is webtool_performance_test? +

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

Can I rate-limit webtool_performance_test? +

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

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

webtool_performance_test is provided by the Webtools MCP Server MCP server (misterboe/webtools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.