browser_select_option
Pick option(s) in a native <select> dropdown. Pass value (matches the option's value attr) OR label (matches its visible text). Lists allowed for multi-select.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-select-option.md
What browser_select_option does on Dialogbrain
AI agents invoke browser_select_option to trigger actions in Dialogbrain. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
ref | string | Yes | |
label | object | — | |
value | object | — | |
page_id | string | Yes |
Parameters from the server's own tool schema.
Why browser_select_option is rated High
This tool performs a browser action (selecting a dropdown option) which constitutes executing an external operation with effects that depend on the arguments passed. It's not merely reading data, and the effect depends on what option is selected in what context. In a unified inbox/agent context, selecting the wrong option could trigger unintended operations, hence medium severity.
From the tool's definition 'Pick option(s) in a native <select> dropdown' — triggers a browser UI interaction/action on a live browser session
Attacks that exploit this kind of access
The rule that runs browser_select_option safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_select_option, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every browser_select_option call is checked against it from then on.
Questions about browser_select_option
Pick option(s) in a native <select> dropdown. Pass value (matches the option's value attr) OR label (matches its visible text). Lists allowed for multi-select. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_select_option accepts 4 parameters: ref, label, value, page_id. Required: ref, page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain 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 Dialogbrain. 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 Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue