High-risk tools in Chrome
4 of the 23 tools in Chrome are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
evaluateExecute 4/5Execute JavaScript in the browser page context. Good uses: computation, style mutations (.style.X = ..., classList.add), shadow-root traversal, in-page fetch(), app-specific sid...
-
navigateExecute 3/5Navigate the ACTIVE tab to a URL (or action:'back' to go back, action:'reload' to refresh current page — all element refs become stale after reload). Waits for settle. WARNING: ...
-
run_planExecute 3/5Execute a sequential plan of tool steps server-side. Supports variables ($varName), conditions (if), saveAs, error strategies (abort/continue/capture_image), suspend/resume. Par...
-
wait_forExecute 4/5Wait for a condition: element visible, network idle, or JS expression true
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Chrome
Enforce policy on Chrome
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init