// SCAN REPORT

Custom Browser

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 03/07/2026

How to control Custom Browser ↓

TOOL MAP

What Custom Browser exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Custom Browser tools

Execute · High seed_auth_session The tool opens a headed (visible) Chromium browser tab, which constitutes triggering an external operation.

1 of Custom Browser's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Custom Browser

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

Cap read operations

{
  "analyze_page": {
    "limits": [
      {
        "counter": "analyze_page_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 Custom Browser — 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 CUSTOM BROWSER →

Instant setup, no code required.

FULL CATALOGUE

All 4 Custom Browser tools

EXECUTE 1 tools

Execute seed_auth_session v0.8.0: opens a headed Chromium tab on

READ 3 tools

Read analyze_page Multi-output bundle MVP: load a source (URL OR inline HTML OR local file/zip) with Playwright (persistent Chro Read to_claude htmltoclaude v0.1: convert a source (URL OR inline HTML OR local file/zip) to a compact YAML DSL (cbm/htmltocl Read to_figma Phase 2 v0.1 DOM→Figma JSON adapter (cbm/htmltofigma/v0). Reuses htmltoclaude walker then maps to Figma REST n

FAQ

Questions about Custom Browser

Is the Custom Browser MCP server safe to use without restrictions? +

The Custom Browser server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Custom Browser MCP server expose? +

4 tools across 1 categories: Read. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Custom Browser? +

Register the Custom Browser 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 Custom Browser tool call.

Deterministic rules across all 4 Custom Browser tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CUSTOM BROWSER →

Instant setup, no code required.

4 Custom Browser tools catalogued and risk-classified — across an index of 43,000+ MCP servers.