mcp-chrome

Control Chrome browser with AI using MCP protocol. Use when users want to automate browser tasks, take screenshots, fill forms, click elements, navigate page...

This skill appears to do what it says (control your existing Chrome), but it requires installing an unpacked Chrome extension and a global native bridge that can read cookies, history, bookmarks, and capture network traffic — this is powerful and risky. Before installing: 1) Verify the publisher and repository (inspect the GitHub repo and npm package author, recent commits, and issues). 2) Review the extension and bridge source code (or ask a trusted reviewer) to confirm they do only the advertised MCP work and do not exfiltrate data. 3) Load and test in a dedicated/sandbox Chrome profile with no sensitive logins or data (or in a disposable VM/container). 4) Limit the agent's autonomy (require user invocation or disable automatic invocation) while you evaluate behavior. 5) After testing, remove the extension and uninstall the global package if not needed. 6) Prefer signed extensions or official store distribution and integrity checks (checksums, signatures). If you cannot verify the code and provenance, treat this as high-risk and avoid installing it in your main browser profile.

Type: OpenClaw Skill Name: mcp-chrome Version: 0.1.1 This skill is classified as suspicious due to its extremely broad and high-privilege access to the user's Chrome browser, including existing login sessions, browsing history, bookmarks, and network traffic. Tools like `chrome_get_web_content` can extract any page content, `chrome_history` accesses sensitive browsing data, and `chrome_network_request` can send HTTP requests with browser cookies to arbitrary external endpoints. While these capabilities are described as part of legitimate browser automation, they present a significant risk for data exfiltration and unauthorized actions if the AI agent is compromised via prompt injection. The installation process also involves globally installing an npm package (`mcp-chrome-bridger`) and loading an unpacked Chrome extension from GitHub, requiring substantial trust in these external components.