performance_start_trace

SERVERChrome DevTools MCP SOURCEanirbandz/chrome_mcp_devtool

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/anirbandz-chrome-mcp-devtool/performance-start-trace.md

WHAT IT DOES

What performance_start_trace does on Chrome DevTools MCP

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

This tool triggers an active operation in the browser (starting a trace recording session) that affects the runtime state of the page. It initiates an ongoing process with side effects on the browser's profiling subsystem. It's not purely read-only (it starts a recording process) but doesn't write/modify user data, making Execute the most appropriate category.

From the tool's definition Starts a performance trace recording on the selected page

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

Starts a performance trace recording on the selected page. This can be used to look for performance problems and insights to improve the performance of the page. It will also report Core Web Vital (CWV) scores for the page. It is categorised as a Execute tool in the Chrome DevTools MCP 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 MCP. 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 (anirbandz/chrome_mcp_devtool). 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 26 Chrome DevTools tools → High-risk tools on this server →

Across the catalogue

start_etw_trace on Procmon →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 →