// SCAN REPORT

Chromium ARM64 Browser

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

2 destructive tools with no built-in limits. Policy required.

Last updated: 4 Jul 2026

18 can modify or destroy data

10 read-only

28 tools total

Community server · catalogue entry verified 04/07/2026

How to control Chromium ARM64 Browser ↓

TOOL MAP

What Chromium ARM64 Browser exposes to your agents

Read (10) Write / Execute (16) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Chromium ARM64 Browser tools

Destructive · Medium wipe_logs The tool irreversibly clears/wipes all stored logs from memory. Destructive · High reset_emulation Reset device emulation back to desktop mode Execute · High evaluate Although the description claims 'read-only operations,' the tool fundamentally executes JavaScript in the browser context. Execute · Medium hover Hovering is an interactive browser action that triggers event listeners (onmouseover, onmouseenter, etc.) and can execute arbitrary JavaScript.

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

POLICY

How to control Chromium ARM64 Browser

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

Deny destructive operations

{
  "reset_emulation": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "close_browser": {
    "limits": [
      {
        "counter": "close_browser_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_console_errors": {
    "limits": [
      {
        "counter": "get_console_errors_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 Chromium ARM64 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 CHROMIUM ARM64 BROWSER →

Instant setup, no code required.

FULL CATALOGUE

All 28 Chromium ARM64 Browser tools

DESTRUCTIVE 2 tools

Destructive reset_emulation Reset device emulation back to desktop mode Destructive wipe_logs Clear all stored logs from memory

EXECUTE 11 tools

Execute click Click an element on the page Execute evaluate Execute JavaScript in the browser (read-only operations) Execute hover Hover over an element on the page Execute navigate Navigate to a URL Execute run_accessibility_audit Run an accessibility audit on the current page Execute run_audit_mode Run comprehensive audit mode for optimization Execute run_best_practices_audit Run a best practices audit on the current page Execute run_debugger_mode Run debugger mode to debug issues in the application Execute run_nextjs_audit Run a Next.js specific audit on the current page Execute run_performance_audit Run a performance audit on the current page Execute start_screencast Start recording a screencast of browser activity. Captures frames via CDP and encodes to MP4/GIF/WebM on stop.

WRITE 5 tools

Write close_browser Close the browser instance Write fill Fill an input field Write select Select an option from a dropdown Write set_cookies Import cookies (e.g. exported after logging in elsewhere) so the browser is authenticated without scripting th Write stop_screencast Stop recording and encode the screencast to a video file. Returns the file path.

READ 10 tools

Read get_console_errors Get browser console errors Read get_console_logs Get browser console logs Read get_content Get page content (HTML or text) Read get_cookies Export all cookies from the current browser session as a JSON array (round-trips with set_cookies). Read get_network_errors Get network error logs Read get_network_logs Get network activity logs Read get_selected_element Get information about the currently selected element Read run_seo_audit Run an SEO audit on the current page Read screencast_status Check screencast recording status: whether recording, frame count, and duration. Read screenshot Take a screenshot of the current page (use fullPage for the entire scrollable length)

EXPLORE

Related servers

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

FAQ

Questions about Chromium ARM64 Browser

Can an AI agent delete data through the Chromium ARM64 Browser MCP server? +

Yes. The Chromium ARM64 Browser server exposes 2 destructive tools including reset_emulation, wipe_logs. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Chromium ARM64 Browser? +

The Chromium ARM64 Browser server has 5 write tools including close_browser, fill, select. 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 Chromium ARM64 Browser.

How many tools does the Chromium ARM64 Browser MCP server expose? +

28 tools across 4 categories: Destructive, Execute, Read, Write. 10 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on Chromium ARM64 Browser? +

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

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

ENFORCE POLICY ON CHROMIUM ARM64 BROWSER →

Instant setup, no code required.

28 Chromium ARM64 Browser tools catalogued and risk-classified — across an index of 43,000+ MCP servers.