Select an option in a dropdown
AI agents invoke browser_select_option to trigger actions in Playwright 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.
Selecting a dropdown option is a browser action that changes the state of a web page form element and may trigger downstream events (onChange handlers, form submissions, page navigation). It is not a simple read, nor does it irreversibly delete data or move money, but it executes an interactive browser operation whose effects depend on which option is selected and the page's behavior.
From the tool's definition 'Select an option in a dropdown' — triggers a UI interaction (selecting a dropdown option) in a live browser session, causing state changes on the web page
Attacks that exploit this kind of access
Select an option in a dropdown. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright 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 Playwright MCP. Nothing to install.
browser_select_option is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
browser_select_option is provided by the Playwright MCP server (lewisvoncken/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →