MCP Server Policy

CHROME DEVTOOLS MCP POLICY

Enforce policies on every tool call to the Chrome DevTools MCP Server. 29 tools listed, categorised, and ready for rules.

ChromeDevTools/chrome-devtools-mcp 10 read 19 write 29 tools total
chrome devtools browser-automation debugging performance

GET STARTED

Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Chrome DevTools.

terminal

# Download policy scaffold

curl -o chrome-devtools.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/chrome-devtools.yaml

# Run with Intercept

intercept --policy chrome-devtools.yaml -- npx -y @ChromeDevTools/chrome-devtools-mcp

Server documentation: https://github.com/ChromeDevTools/chrome-devtools-mcp

READ TOOLS

10

WRITE TOOLS

11

type_text

type_text Enter text character-by-character

resize_page

resize_page Adjust viewport dimensions

EXECUTE TOOLS

8

navigate_page

navigate_page Load a URL

new_page

new_page Open a new page

select_page

select_page Switch between pages

close_page

close_page Close a browser page

POLICY YAML

This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.

chrome-devtools.yaml 
version: "1"
description: "Policy for ChromeDevTools/chrome-devtools-mcp"
default: "allow"
tools:
    list_pages:
        rules: []
    take_screenshot:
        rules: []
    take_snapshot:
        rules: []
    list_console_messages:
        rules: []
    get_console_message:
        rules: []
    list_network_requests:
        rules: []
    get_network_request:
        rules: []
    take_memory_snapshot:
        rules: []
    performance_analyze_insight:
        rules: []
    lighthouse_audit:
        rules: []
    click:
        rules: []
    drag:
        rules: []
    fill:
        rules: []
    fill_form:
        rules: []
    handle_dialog:
        rules: []
    hover:
        rules: []
    press_key:
        rules: []
    type_text:
        rules: []
    upload_file:
        rules: []
    resize_page:
        rules: []
    emulate:
        rules: []
    navigate_page:
        rules: []
    new_page:
        rules: []
    select_page:
        rules: []
    close_page:
        rules: []
    wait_for:
        rules: []
    evaluate_script:
        rules: []
    performance_start_trace:
        rules: []
    performance_stop_trace:
        rules: []

RELATED POLICIES

Sentry 25 tools
debugging
BrowserTools 15 tools
debugging
Time 2 tools
devtools
Fetch 1 tools
devtools

FREQUENTLY ASKED QUESTIONS

What tools does the Chrome DevTools MCP server expose?

The Chrome DevTools MCP Server exposes 29 tools across 3 categories: Read, Write, Execute. Each tool can be individually controlled with Intercept policies.

How do I enforce policies on Chrome DevTools?

Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Chrome DevTools MCP server. Every tool call is evaluated against your YAML policy before execution.

Is the Chrome DevTools policy free to use?

Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.

ENFORCE POLICIES ON CHROME DEVTOOLS

Open source. One binary. Zero dependencies.

VIEW ON GITHUB Browse all policies →