handle_dialog · Opera DevTools MCP: Risk & Policy

WHAT IT DOES

What handle_dialog does on Opera DevTools MCP

AI agents invoke handle_dialog to trigger actions in Opera DevTools MCP. 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 handle_dialog needs a policy

Handling a browser dialog (accept/dismiss/prompt response) is an interactive browser action that can have downstream effects depending on what the dialog was for (e.g., confirming a destructive action, submitting a form). This falls under Execute as it triggers an external browser operation. Severity is medium because misuse could confirm unintended actions in the browser.

From the tool's definition 'handle it' referring to a browser dialog — triggers an external browser operation (accept/dismiss dialog) whose effect depends on arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

handle_dialog Rate-limited

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": {
    "handle_dialog": {
      "limits": [
        {
          "counter": "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 Opera DevTools MCP, so you can run agents against it safely.

FAQ

Questions about handle_dialog

What does the handle_dialog tool do? +

If a browser dialog was opened, use this command to handle it. It is categorised as a Execute tool in the Opera DevTools MCP 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 Opera 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 Opera DevTools MCP. 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 Opera DevTools MCP server (operasoftware/opera-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.