performance_start_trace

Start a performance trace on the selected webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed.

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/performance-start-trace.md

WHAT IT DOES

What performance_start_trace does on Chrome Devtools

AI agents invoke performance_start_trace to trigger actions in Chrome Devtools. 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.

RISK

Why performance_start_trace is rated High

Starting a performance trace is an active operation that instruments and monitors a webpage, executing browser-level tracing logic. While not destructive or financial, it modifies the execution environment of the page and could be misused to extract sensitive timing data, trigger side effects during trace collection, or interfere with page functionality.

From the tool's definition Tool description states 'Start a performance trace on the selected webpage' – this triggers external operations (Chrome DevTools tracing) that depend on runtime arguments and affects the target page's behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs performance_start_trace safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For performance_start_trace, this is the rule to start with:

performance_start_trace Rate-limited

performance_start_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": {
    "performance_start_trace": {
      "limits": [
        {
          "counter": "performance_start_trace_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every performance_start_trace call is checked against it from then on.

FAQ

Questions about performance_start_trace

What does the performance_start_trace tool do? +

Start a performance trace on the selected webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on performance_start_trace? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for performance_start_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 Chrome Devtools. Nothing to install.

What risk level is performance_start_trace? +

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

Can I rate-limit performance_start_trace? +

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

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

performance_start_trace is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →