CHROME DEVTOOLS MCP SERVER TOOLS

24 tools from the Chrome DevTools MCP Server MCP Server, categorised by risk level.

View the Chrome DevTools MCP Server policy →

// ALL 24 CHROME DEVTOOLS MCP SERVER TOOLS

READ 15 tools

Read get_console_logs Get console output logs including errors, warnings, and log messages. Essential for debugging JavaScript is... Read get_dom_tree Get the DOM tree structure of the current page. Useful for understanding page structure and debugging. Read get_enabled_domains Get the status of enabled Chrome DevTools domains Read get_network_logs Get network request logs including requests and responses. Useful for debugging API calls and network issues. Read get_page_functions Get all functions defined in the current page. Useful for understanding what functions are available to debug. Read get_page_info Get basic page information including title, URL, and meta tags Read get_paused_info Get information about the paused state when debugger is paused Read get_script_source Get the source code of a specific script. Use this to read JavaScript code before setting breakpoints. Read get_script_sources Get all JavaScript sources loaded in the current page. Useful for understanding code structure before setti... Read list_available_targets List all available Chrome tabs/pages with their WebSocket URLs. Useful for switching between different debu... Read list_breakpoints List all active breakpoints Read query_elements Query DOM elements using CSS selectors. Returns element information and content. Read search_in_scripts Search for functions, classes, or patterns in all loaded JavaScript code. Helps locate where to set breakpo... Read step_over Step over the current line when debugger is paused Read take_screenshot Take a screenshot of the current page. Useful for visual debugging and verification.

WRITE 5 tools

Write close_chrome Close the Chrome browser instance Write connect_remote_chrome Connect to a remote Chrome/Chromium instance (e.g., Electron app) via Chrome DevTools Protocol. Use this in... Write connect_websocket_url Connect directly to Chrome DevTools using a WebSocket debugger URL. This allows switching between different... Write resume_execution Resume execution when debugger is paused Write set_breakpoint Set a JavaScript breakpoint at a specific location. Supports both pausing breakpoints and non-pausing log b...

DESTRUCTIVE 1 tools

Destructive remove_breakpoint Remove a breakpoint

EXECUTE 3 tools

Execute execute_javascript Execute JavaScript code in the page context. Can be used to interact with the page, modify DOM, or test fun... Execute launch_chrome Launch a Chrome browser instance for development and debugging. This is the starting point for frontend dev... Execute navigate_to Navigate to a specific URL in the Chrome browser

// FAQ

How many tools does the Chrome DevTools MCP Server MCP server have? +

The Chrome DevTools MCP Server MCP server exposes 24 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Chrome DevTools MCP Server tools? +

Route the Chrome DevTools MCP Server server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Chrome DevTools MCP Server tools fall into? +

Chrome DevTools MCP Server tools are categorised as Read (15), Write (5), Destructive (1), Execute (3). Each category has a recommended default policy.

Enforce policy on every Chrome DevTools MCP Server tool call.

Start from Chrome DevTools MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Instant setup, no code required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.