handle_dialog
If a browser dialog was opened, use this command to handle it
This record as markdown: /tools/async23-chrome-devtools-mcp/handle-dialog.md
What handle_dialog does on Chrome Devtools
AI agents invoke handle_dialog to trigger actions in Chrome Devtools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why handle_dialog is rated High
This tool triggers an external browser action (accepting or dismissing a dialog) whose effect depends on arguments. It is not purely read-only and can influence browser state and page flow, making it Execute. Misuse could cause unintended form submissions or confirmation of destructive browser dialogs, but blast radius is limited to the current page session.
From the tool's definition handle_dialog - 'If a browser dialog was opened, use this command to handle it'
Attacks that exploit this kind of access
The rule that runs handle_dialog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For handle_dialog, this is the rule to start with:
handle_dialog stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every handle_dialog call is checked against it from then on.
Questions about handle_dialog
If a browser dialog was opened, use this command to handle it. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for handle_dialog: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Chrome Devtools. Nothing to install.
handle_dialog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the handle_dialog rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for handle_dialog. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
handle_dialog is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
Across the catalogue