performance_stop_trace

What performance_stop_trace does on Chrome DevTools MCP

AI agents invoke performance_stop_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.

Why performance_stop_trace is rated High

This tool executes a command that affects browser state and monitoring infrastructure. While not destructive (the trace data itself persists), it irreversibly changes the recording state and could interfere with performance diagnostics if misused by an AI agent. It fits Execute rather than Write because it triggers an external operation (trace termination) whose effects are system-level rather than data-creation.

From the tool's definition Stops an active performance trace recording; this is an operational action that modifies the state of the Chrome DevTools tracing system, triggering external effects (terminating an ongoing recording session).

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "performance_stop_trace": {
      "limits": [
        {
          "counter": "performance_stop_trace_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about performance_stop_trace