Chrome Mcp

This skill appears internally consistent with its purpose, but it gives the agent potent access to your real browser sessions and lets it execute JavaScript inside pages. Before installing or using it, consider: - Only enable if you fully trust the skill and the agent that will invoke it. Treat trust carefully because the agent can read and act in any logged-in site. - Enable Chrome remote debugging only for a short period and only on a dedicated browser profile (create a separate Chrome profile with no sensitive logins). - Prefer manual, user-invoked use over autonomous invocation. If possible, disable autonomous invocation or require explicit user approval for every action. - Avoid using this skill while logged into sensitive accounts (banking, primary email, corporate SSO). - Limit actions to read-only where possible and avoid granting it permission to post or delete on social accounts unless you trust it. - Monitor network activity and running devtools ports; close the remote-debugging port when done. If you want a lower-risk setup, run Chrome in a disposable profile or a VM/container and keep all sensitive accounts out of that profile. If you need more assurance, request additional details from the skill author (how the chrome__* tools are provided/secured, whether there are safeguards to limit origins/actions, and why autonomous invocation is necessary).