Skip to main content

Chrome DevTools

Drive a real Chrome browser: click, fill forms, read the console, and inspect network calls.

Tools

26 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

26 tools found.

  • Click

    Tool name: click

    Clicks on the provided element

  • Close page

    Tool name: close_page

    Closes the page by its index.

  • Drag

    Tool name: drag

    Drag an element onto another element

  • Emulate

    Tool name: emulate

    Emulates various features on the selected page.

  • Evaluate script

    Tool name: evaluate_script

    Evaluate a JavaScript function inside the currently selected page.

  • Fill

    Tool name: fill

    Type text into a input, text area or select an option from a element.

  • Fill form

    Tool name: fill_form

    Fill out multiple form elements at once

  • Get console message

    Read only

    Tool name: get_console_message

    Gets a console message by its ID.

  • Get network request

    Read only

    Tool name: get_network_request

    Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel.

  • Handle dialog

    Tool name: handle_dialog

    Handle dialog.

  • Hover

    Tool name: hover

    Hover over the provided element

  • List console messages

    Read only

    Tool name: list_console_messages

    List all console messages for the currently selected page since the last navigation.

  • List network requests

    Read only

    Tool name: list_network_requests

    List all requests for the currently selected page since the last navigation.

  • List pages

    Read only

    Tool name: list_pages

    Get a list of pages open in the browser.

  • Navigate page

    Tool name: navigate_page

    Navigates the currently selected page to a URL.

  • New page

    Tool name: new_page

    Creates a new page

  • Performance analyze insight

    Read only

    Tool name: 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.

  • Performance start trace

    Read only

    Tool name: performance_start_trace

    Starts a performance trace recording on the selected page.

  • Performance stop trace

    Read only

    Tool name: performance_stop_trace

    Stops the active performance trace recording on the selected page.

  • Press key

    Tool name: press_key

    Press a key or key combination.

  • Resize page

    Tool name: resize_page

    Resizes the selected page's window so that the page has specified dimension

  • Select page

    Read only

    Tool name: select_page

    Select a page as a context for future tool calls.

  • Take screenshot

    Tool name: take_screenshot

    Take a screenshot of the page or element.

  • Take snapshot

    Tool name: take_snapshot

    Take a text snapshot of the currently selected page based on the a11y tree.

  • Upload file

    Tool name: upload_file

    Upload a file through a provided element.

  • Wait for

    Read only

    Tool name: wait_for

    Wait for the specified text to appear on the selected page.

Compatibility

Connect Chrome DevTools to the clients your teams already use

19 AI clients can connect to Chrome DevTools through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Chrome DevTools through Runlayer?

One approved path

Approve Chrome DevTools once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions