browser_select_option · Browser Pool MCP: Risk & Policy

WHAT IT DOES

What browser_select_option does on Browser Pool

AI agents invoke browser_select_option 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_select_option needs a policy

Selecting an option in a browser form is a browser action that can trigger onChange handlers, form submissions, or other side effects depending on the page context. It falls under Execute as it drives external browser operations, with medium severity since the impact depends on what form/page is being interacted with.

From the tool's definition 'Select option' — triggers a browser UI interaction (selecting a dropdown/listbox option) within a Playwright session, constituting an external browser action whose effects depend on arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_select_option Rate-limited

browser_select_option 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_select_option": {
      "limits": [
        {
          "counter": "browser_select_option_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_select_option

What does the browser_select_option tool do? +

Select option. 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_select_option? +

Register the Browser Pool MCP server in PolicyLayer and add a rule for browser_select_option: 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_select_option? +

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

Can I rate-limit browser_select_option? +

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

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

browser_select_option 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.