29 tools from the Chrome Devtools MCP Server, categorised by risk level.
View the Chrome Devtools policy →get_console_message Gets a console message by its ID. You can get all messages by calling list_console_messages. get_network_request Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel. list_console_messages List all console messages for the currently selected page since the last navigation. list_network_requests List all requests for the currently selected page since the last navigation. list_pages Get a list of pages open in the browser. take_memory_snapshot Capture a heap snapshot of the currently selected page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks. 2/5 take_screenshot Take a screenshot of the page or element. 2/5 take_snapshot Take a text snapshot of the currently selected page based on the a11y tree. The snapshot lists page elements along with a unique
identifier (uid). ... 2/5 click Clicks on the provided element 2/5 close_page Closes the page by its index. The last open page cannot be closed. 2/5 drag Drag an element onto another element 2/5 evaluate_script Evaluate a JavaScript function inside the currently selected page. Returns the response as JSON,
so returned values have to be JSON-serializable. 2/5 fill Type text into a input, text area or select an option from a <select> element. 2/5 fill_form Fill out multiple form elements at once 2/5 handle_dialog If a browser dialog was opened, use this command to handle it 2/5 hover Hover over the provided element 2/5 press_key Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special... 2/5 resize_page Resizes the selected page's window so that the page has specified dimension 2/5 select_page Select a page as a context for future tool calls. 2/5 type_text Type text using keyboard into a previously focused input 2/5 upload_file Upload a file through a provided element. 3/5 emulate Emulates various features on the selected page. 3/5 lighthouse_audit Get Lighthouse score and reports for accessibility, SEO and best practices. This excludes performance. For performance audits, run performance_star... 3/5 navigate_page Go to a URL, or back, forward, or reload. Use project URL if not specified otherwise. 3/5 new_page Open a new tab and load a URL. Use project URL if not specified otherwise. 3/5 performance_analyze_insight Provides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording. 3/5 performance_start_trace Start a performance trace on the selected webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load ... 4/5 performance_stop_trace Stop the active performance trace recording on the selected webpage. 4/5 wait_for Wait for the specified text to appear on the selected page. 3/5 The Chrome Devtools MCP server exposes 29 tools across 3 categories: Read, Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Chrome Devtools server.
Chrome Devtools tools are categorised as Read (8), Write (13), Execute (8). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept