// SCAN REPORT

Chrome Profile MCP Server

18 tools. 15 can modify or destroy data without limits.

15 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

15 can modify or destroy data

3 read-only

18 tools total

Community server · catalogue entry verified 03/07/2026

How to control Chrome Profile MCP Server ↓

TOOL MAP

What Chrome Profile MCP Server exposes to your agents

Read (3) Write / Execute (15) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Chrome Profile MCP Server tools

Execute · Critical evaluate_js This tool runs arbitrary code (JavaScript) in the context of a real Chrome browser instance. Execute · High navigate While navigation might seem like a simple 'Read' operation, it is classified as Execute because: (1) it triggers external side effects (loading a URL, executing page scripts, setting cookies, triggering redirects); (2) t Execute · High new_tab While opening a tab alone might seem Write-like, the capability to navigate to arbitrary URLs transforms this into Execute category. Execute · High wait_for The wait_for tool executes browser automation that can block execution flow and trigger cascading page interactions.

15 of Chrome Profile MCP Server's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Chrome Profile MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome Profile MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "close_tab": {
    "limits": [
      {
        "counter": "close_tab_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_page_content": {
    "limits": [
      {
        "counter": "get_page_content_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Chrome Profile MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CHROME PROFILE →

Instant setup, no code required.

FULL CATALOGUE

All 18 Chrome Profile MCP Server tools

EXECUTE 13 tools

Execute click Click an element by CSS selector Execute evaluate_js Execute JavaScript code in the page context and return the result Execute go_back Go back in browser history Execute go_forward Go forward in browser history Execute hover Hover over an element Execute navigate Navigate active tab to a URL Execute new_tab Open a new tab, optionally navigating to a URL Execute press_key Press a keyboard key (e.g. Enter, Tab, Escape, ArrowDown) Execute reload Reload current page Execute scroll Scroll the page or a specific element into view Execute select_option Select an option from a dropdown Execute switch_tab Switch active tab by index Execute wait_for Wait for an element to appear on the page

WRITE 2 tools

Write close_tab Close a tab by index (defaults to active tab) Write type Type text into an input element

READ 3 tools

Read get_page_content Get page HTML or text content of a specific element Read list_tabs List all open tabs with their URLs Read screenshot Take a screenshot of the current page or a specific element

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Chrome Profile MCP Server

How do I prevent bulk modifications through Chrome Profile MCP Server? +

The Chrome Profile MCP Server server has 2 write tools including close_tab, type. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Chrome Profile MCP Server.

How many tools does the Chrome Profile MCP Server MCP server expose? +

18 tools across 3 categories: Execute, Read, Write. 3 are read-only. 15 can modify, create, or delete data.

How do I enforce a policy on Chrome Profile MCP Server? +

Register the Chrome Profile MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Chrome Profile MCP Server tool call.

Deterministic rules across all 18 Chrome Profile MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CHROME PROFILE →

Instant setup, no code required.

18 Chrome Profile MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.