MCP Tool Reference High Risk

performance_stop_trace

Stop trace recording

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

ChromeDevTools/chrome-devtools-mcp Execute

WHEN AI AGENTS USE THIS TOOL

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

WHY ENFORCE A POLICY ON PERFORMANCE_STOP_TRACE

performance_stop_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.

RECOMMENDED POLICY

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

chrome-devtools.yaml 
tools:
  performance_stop_trace:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Chrome DevTools policy for all 29 tools.

DETAILS

Tool Name

performance_stop_trace

Category

Execute

MCP Server

Chrome DevTools MCP Server

Risk Level

High

MORE CHROME DEVTOOLS TOOLS

navigate_page Execute
Load a URL
new_page Execute
Open a new page
select_page Execute
Switch between pages
close_page Execute
Close a browser page
wait_for Execute
Wait for specific conditions
evaluate_script Execute
Execute JavaScript
performance_start_trace Execute
Start recording a trace
list_pages Read
List open pages

View all 29 tools →

SIMILAR EXECUTE TOOLS ON OTHER SERVERS

call-actor Apify
Call an Actor and get its run results
boot_simulator Appium
Boot an iOS simulator
setup_wda Appium
Download and setup WebDriverAgent for iOS simulators
install_wda Appium
Install and launch WebDriverAgent on an iOS simulator
auth0_deploy_action Auth0
Deploy an Auth0 action
auth0_publish_form Auth0
Publish an Auth0 form

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the performance_stop_trace tool do?

Stop trace recording. 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?

Add a rule in your Intercept YAML policy under the tools section for performance_stop_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_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 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_stop_trace completely?

Set action: deny in the Intercept 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 (ChromeDevTools/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.

VIEW ON GITHUB Full Chrome DevTools policy →