High Risk →

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.

Accepts file system path (filePath)

Part of the Chrome Devtools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

chrome-devtools-mcp Execute Risk 4/5

AI agents invoke performance_start_trace to trigger processes or run actions in Chrome Devtools. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

performance_start_trace can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-chromedevtools-chrome-devtools-mcp.yaml
tools:
  performance_start_trace:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Chrome Devtools policy for all 29 tools.

Tool Name performance_start_trace
Category Execute
Risk Level High

View all 29 tools →

Agents calling execute-class tools like performance_start_trace have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

performance_start_trace is one of the high-risk operations in Chrome Devtools. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

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? +

Add a rule in your Intercept YAML policy under the tools section for performance_start_trace. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chrome Devtools MCP server.

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 Intercept 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 Intercept 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 (chrome-devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Chrome Devtools

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.