29 tools from the Chrome DevTools MCP Server, categorised by risk level.
View the Chrome DevTools policy →get_console_message Access a specific console message by ID 2/5 get_network_request Get details of a specific network request 2/5 list_console_messages View all console log entries 2/5 list_network_requests View all network activity 2/5 list_pages List open browser pages 2/5 performance_analyze_insight Extract performance data from the page 2/5 performance_stop_trace Stop trace recording and get results 2/5 take_memory_snapshot Capture memory state for analysis 2/5 take_screenshot Capture a screenshot of the current page 2/5 take_snapshot Document current page state as HTML snapshot 2/5 wait_for Wait for a specific condition on the page 2/5 click Click on a page element 4/5 drag Drag an element on the page 4/5 emulate Simulate different devices and network conditions 3/5 evaluate_script Execute arbitrary JavaScript on the page 5/5 fill Input text into a form field 4/5 fill_form Complete an entire form with values 5/5 handle_dialog Accept or dismiss browser dialogs 4/5 hover Trigger hover state on an element 3/5 lighthouse_audit Run Lighthouse audit checks on the page 3/5 navigate_page Navigate to a URL in the browser 5/5 new_page Open a new browser page 4/5 performance_start_trace Start recording a performance trace 3/5 press_key Simulate keyboard input on the page 4/5 type_text Enter text character-by-character 4/5 upload_file Upload a file through a form input 5/5 The Chrome DevTools MCP server exposes 29 tools across 4 categories: Read, Write, Destructive, 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 (11), Write (2), Destructive (1), Execute (15). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept