DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-write
apireno DOMShell
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| apireno DOMShell |
| No fix yet |
Original description
DOMShell is a Chrome automation project whose MCP server exposes Unix-style tools for AI agents. Prior to 2.0.8, the DOMShell MCP server classifies the domshell_eval tool and eval command as read-tier operations that can run without --allow-write, even though eval shares the Runtime.evaluate dispatch path with the write-tier js command and has no side-effect gate. An MCP caller with tool-session access can therefore use domshell_eval to mutate DOM, window, or global state while the host approval interface, server authorization flags, denial messages, and audit records represent the operation as read-only. The bypass does not expose a capability beyond domshell_js for callers already authorized to write, but it violates the configured permission boundary for callers lacking that authorization. This issue is fixed in version 2.0.8.
From the CVE record · GitHub_M