browser_handle_dialog
5 registry entries were observed exposing a tool named browser_handle_dialog — none of them flagged as a privileged capability.
Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,342 of 40,590 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.
- v1.30.1↓ 2k/wk★ 53
Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
ClaudeCursorCopilotGeminimcp - v1.1.1★ 56
MCP server for automated web accessibility scanning with Playwright and Axe-core.
ClaudeCursorCopilotGeminimcp - v1.2.1★ 50
MCP server + Chrome extension for AI browser control with real sessions.
ClaudeCursorCopilotGeminimcp - v1.1.3↓ 156/wk★ 1
Fork of mcp-patchright that adds a per-call world:'main' option to browser_evaluate / browser_run_code_unsafe, so page-defined window globals are visible and callable. Defaults to Patchright's isolated stealth world; opt into main only when you need it. E
ClaudeCursorCopilotGeminipatchrightmcpstealthbrowserplaywrightautomation - v0.4.3
Browser MCP: drive a real Chromium via Playwright with compact ref-addressable page snapshots
ClaudeCursorCopilotGeminimcp
All indexed toolsSearch the registry for browser_handle_dialog