browser_handle_dialog
Respond to a pending JS dialog (alert/confirm/prompt). Pass accept=true for OK or false for Cancel. For prompt() dialogs also pass prompt_text. Dialogs are queued at page-open time; returns {pending: false} if none is waiting.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-handle-dialog.md
What browser_handle_dialog does on Dialogbrain
AI agents invoke browser_handle_dialog to trigger actions in Dialogbrain. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
accept | boolean | Yes | |
page_id | string | Yes | |
prompt_text | object | — |
Parameters from the server's own tool schema.
Why browser_handle_dialog is rated High
This tool interacts with live browser dialog boxes, triggering browser-level UI actions (accepting or dismissing JS dialogs). This is an Execute-category action because it drives external browser operations whose effects depend on the arguments passed. Misuse could confirm destructive in-page actions (e.g., accepting a 'delete all data?' confirm dialog), giving it high severity.
From the tool's definition "Respond to a pending JS dialog (alert/confirm/prompt). Pass accept=true for OK or false for Cancel."
Attacks that exploit this kind of access
The rule that runs browser_handle_dialog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_handle_dialog, this is the rule to start with:
browser_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 Dialogbrain, apply this rule, and every browser_handle_dialog call is checked against it from then on.
Questions about browser_handle_dialog
Respond to a pending JS dialog (alert/confirm/prompt). Pass accept=true for OK or false for Cancel. For prompt() dialogs also pass prompt_text. Dialogs are queued at page-open time; returns {pending: false} if none is waiting. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_handle_dialog accepts 3 parameters: accept, page_id, prompt_text. Required: accept, page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for browser_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 Dialogbrain. Nothing to install.
browser_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 browser_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 browser_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.
browser_handle_dialog is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue