performance_stop_trace

Stop the active performance trace recording on the selected webpage.

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-stop-trace.md

WHAT IT DOES

What performance_stop_trace does on Chrome Devtools

AI agents invoke performance_stop_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_stop_trace is rated High

While stopping a trace is not destructive (the trace data may already be collected), it is an Execute action because it triggers an operation on an external system (the browser's performance monitoring) and could affect what data is captured or available.

From the tool's definition Tool stops an active performance trace recording, which involves triggering an external operation (halting a browser performance monitoring action) whose effects depend on the browser state and the context of what is being traced.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs performance_stop_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_stop_trace, this is the rule to start with:

performance_stop_trace Rate-limited

performance_stop_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_stop_trace": {
      "limits": [
        {
          "counter": "performance_stop_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_stop_trace call is checked against it from then on.

FAQ

Questions about performance_stop_trace

What does the performance_stop_trace tool do? +

Stop the active performance trace recording on the selected webpage. 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_stop_trace? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for performance_stop_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_stop_trace? +

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

Can I rate-limit performance_stop_trace? +

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

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

performance_stop_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

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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