browser_handle_dialog · Browser Pool MCP: Risk & Policy

WHAT IT DOES

What browser_handle_dialog does on Browser Pool

AI agents invoke browser_handle_dialog to trigger actions in Browser Pool. 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 IT NEEDS A POLICY

Why browser_handle_dialog needs a policy

Handling a dialog is a browser action that triggers an external interaction, accepting or dismissing dialogs which can affect the state of the web application. It falls under Execute as it performs a browser action whose effect depends on arguments (e.g., accepting vs. dismissing, input to prompt dialogs). Description is sparse, lowering confidence slightly.

From the tool's definition 'Handle dialog' — interacts with browser dialogs (alert/confirm/prompt) as part of a Playwright browser automation session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_handle_dialog Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_handle_dialog": {
      "limits": [
        {
          "counter": "browser_handle_dialog_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Browser Pool, so you can run agents against it safely.

FAQ

Questions about browser_handle_dialog

What does the browser_handle_dialog tool do? +

Handle dialog. It is categorised as a Execute tool in the Browser Pool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_handle_dialog? +

Register the Browser Pool 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 Browser Pool. Nothing to install.

What risk level is browser_handle_dialog? +

browser_handle_dialog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_handle_dialog? +

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.

How do I block browser_handle_dialog completely? +

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.

What MCP server provides browser_handle_dialog? +

browser_handle_dialog is provided by the Browser Pool MCP server (omgeverdo/browser-pool-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.