webtool_performance_trace · Webtools MCP Server MCP

WHAT IT DOES

What webtool_performance_trace does on Webtools MCP Server

AI agents invoke webtool_performance_trace 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_trace needs a policy

The tool executes performance profiling and tracing operations that instrument and measure runtime behavior of JavaScript, DOM, layout cycles, and resource loading. While non-destructive and read-focused in intent, it triggers external operations (profiling hooks, performance measurement API calls) whose effects depend on the target URL and page state arguments.

From the tool's definition Performs detailed performance analysis with execution of tracing modules for layout thrashing, JavaScript execution timeline analysis, memory and DOM growth monitoring, and resource loading inspection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

webtool_performance_trace Rate-limited

webtool_performance_trace 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_trace": {
      "limits": [
        {
          "counter": "webtool_performance_trace_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_trace

What does the webtool_performance_trace tool do? +

Perform a detailed performance analysis with specialized modules for layout thrashing, CSS variables impact, JavaScript execution timeline, long tasks breakdown, memory and DOM growth analysis, and resource loading optimization. Provides actionable recommendations for performance improvements. 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_trace? +

Register the Webtools MCP Server MCP server in PolicyLayer and add a rule for webtool_performance_trace: 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_trace? +

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

Can I rate-limit webtool_performance_trace? +

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

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

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