← MCP server and skill grades

js-reverse-mcp

zhizhuodemao/js-reverse-mcp

B
Type
MCP server
Scanned
Nov 12, 2026
Version
bf7dc506e874
Files read
90

This MCP server lets an AI coding agent control a Chrome browser over DevTools to inspect scripts, debug breakpoints, capture HTTP and WebSocket traffic, and run JavaScript on web pages. By default, local file access is unrestricted and TLS certificate checks are disabled in the launched browser, allowing a webpage that tricks the agent or an attacker on the local network to read or overwrite files on your computer or intercept HTTPS sessions.

What it can reach

Browser
Launches and controls Chrome (using a persistent profile at ~/.cache/chrome-devtools-mcp/chrome-profile by default) or connects to an existing CDP endpoint to navigate pages, click elements, debug scripts, read or clear cookies and site storage, capture screenshots, and record HTTP and WebSocket traffic.
Files
Reads local files up to 10 MiB via evaluate_script and writes saved scripts, network captures, evaluation results, screenshots, logs, and browser profiles to disk, across the entire user filesystem unless --allowedRoots is configured.
Network
Makes arbitrary HTTP, HTTPS, and WebSocket connections through the controlled browser to any site visited, and downloads a prebuilt CloakBrowser binary when --cloak is enabled.

Findings

2 medium1 low
  1. MediumUnrestricted local file read, write, and file:// navigation by default

    src/LocalFileAccess.ts:44

    Unless the user manually passes --allowedRoots (which is omitted from the default Quick Start configuration), host file reads, file writes, and file:// browser navigations have no directory boundary. Because this server feeds untrusted webpage scripts, console messages, and network payloads into the AI agent, prompt injection on an inspected webpage can trick the agent into reading sensitive host files (such as SSH keys or cloud credentials) via evaluate_script localFilePath or file:// pages and sending them to an external server, or writing attacker-controlled response data over shell startup files, authorized_keys, or Git hooks. The confirm and confirmOverwrite tool parameters do not block a tricked agent because the agent supplies those boolean flags itself.

    Fix: Pass --allowedRoots pointing to a dedicated empty workspace folder (along with --isolated) in your MCP configuration, and change the server default so local file access is restricted to a dedicated workspace unless explicitly opted out.

  2. MediumTLS certificate verification disabled in launched browsers

    src/browser.ts:172

    When launching Chrome or CloakBrowser, the server hardcodes ignoreHTTPSErrors: true on the browser context with no CLI option to re-enable certificate validation. The controlled browser silently accepts expired, self-signed, or wrong-domain HTTPS certificates without error. Because default mode also reuses a persistent profile with saved logins, an attacker on the same Wi-Fi or network path can intercept HTTPS traffic, steal session cookies, or inject malicious scripts and prompt injections into visited pages.

    Fix: Set ignoreHTTPSErrors to false by default and provide an explicit --ignoreHttpsErrors CLI flag for users who need to debug self-signed targets.

  3. LowOptional --cloak mode downloads and runs a third-party browser binary at runtime

    src/cloak.ts:133

    When started with the optional --cloak flag, the server imports the unpinned optional dependency cloakbrowser (^0.4.10), downloads a ~200 MB custom-compiled Chromium executable from an external host on first run, and launches it on the user's machine. Compromising either the unpinned npm package or its binary download mirror would execute native code on the host for users who enable --cloak.

    Fix: Pin cloakbrowser to an exact version in package.json and verify a pinned cryptographic checksum before executing any downloaded browser binary, or avoid passing --cloak unless you trust CloakBrowser's release pipeline.