handle_popup · MCP Selenium WebDriver MCP: Risk & Policy

WHAT IT DOES

What handle_popup does on MCP Selenium WebDriver

AI agents invoke handle_popup to trigger actions in MCP Selenium WebDriver. 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_popup needs a policy

Given the server context (Selenium WebDriver browser automation), 'handle_popup' almost certainly interacts with browser popups — accepting, dismissing, or otherwise manipulating dialog boxes. This constitutes a browser action/execution. Description is empty, so confidence is reduced, but the sibling tools (click_element, execute_script) confirm an Execute-category server.

From the tool's definition Tool name 'handle_popup' on a Selenium WebDriver MCP server with browser automation capabilities; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

handle_popup Rate-limited

handle_popup 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_popup": {
      "limits": [
        {
          "counter": "handle_popup_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 MCP Selenium WebDriver, so you can run agents against it safely.

FAQ

Questions about handle_popup

What does the handle_popup tool do? +

handle_popup. It is categorised as a Execute tool in the MCP Selenium WebDriver 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_popup? +

Register the MCP Selenium WebDriver MCP server in PolicyLayer and add a rule for handle_popup: 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 MCP Selenium WebDriver. Nothing to install.

What risk level is handle_popup? +

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

Can I rate-limit handle_popup? +

Yes. Add a rate_limit block to the handle_popup 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_popup completely? +

Set action: deny in the PolicyLayer policy for handle_popup. 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_popup? +

handle_popup is provided by the MCP Selenium WebDriver MCP server (nixon-suarez/mcp-selenium-webdriver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.