handle_dialog

THE RISK

High Risk

Why handle_dialog needs a policy

This tool interacts with browser dialogs by accepting or dismissing them, triggering external browser operations. It can confirm or deny dialogs which may have side effects depending on what the dialog is prompting (e.g., confirming a destructive action, submitting a form). It's an Execute-category action as it triggers browser-level operations whose effects depend on arguments and context.

From the tool's definition Handle a native browser dialog (alert/confirm/prompt). Use this when a dialog is blocking page interaction.

Documented attack patterns abuse exactly the kind of access handle_dialog gives an agent:

POLICY

How to control handle_dialog

PolicyLayer is an MCP gateway — it sits between your AI agents and Webclaw, and nothing reaches the server without passing your rules. This is the rule we recommend for handle_dialog:

policy.json

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

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.

Create a free account and register Webclaw — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Webclaw tools

Destructive close_tab Close a browser tab Execute drop_files Drop files onto an element (file input or drag-and-drop target) for uploading Execute hover Hover over an element to trigger mouseover events and reveal hidden UI (e.g., dropdown men Execute invoke_webmcp_tool Invoke a WebMCP tool declared by the current page Execute navigate_to Navigate the browser to a URL Execute new_tab Open a new browser tab Execute wait_for_navigation Wait for the current page to finish loading Execute click Click an element identified by its @ref from the latest page snapshot

All 21 Webclaw tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Webclaw → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about handle_dialog

What does the handle_dialog tool do? +

Handle a native browser dialog (alert/confirm/prompt). Use this when a dialog is blocking page interaction. It is categorised as a Execute tool in the Webclaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on handle_dialog? +

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

What risk level is handle_dialog? +

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

Can I rate-limit handle_dialog? +

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.

How do I block handle_dialog completely? +

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.

What MCP server provides handle_dialog? +

handle_dialog is provided by the Webclaw MCP server (kuroko1t/webclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Webclaw tool call.

Start from Webclaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →