browse_select
Select an <option> value in a dropdown by @eN ref.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse-select.md
What browse_select does on Gateway
AI agents invoke browse_select to trigger actions in Gateway. 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 | an @eN ref (a <select>) |
value | string | Yes | option value to choose |
browser_id | string | Yes | from browse_open |
Parameters from the server's own tool schema.
Why browse_select is rated High
This tool performs a browser action (selecting a dropdown option), which constitutes an Execute-category operation. It interacts with an external browser environment and can trigger side effects depending on what the dropdown selection does (form submissions, UI state changes, etc.). Severity is medium because misuse could cause unintended selections in web forms or applications being automated.
From the tool's definition Select an <option> value in a dropdown by @eN ref — triggers a browser interaction/DOM action
Attacks that exploit this kind of access
The rule that runs browse_select safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_select, this is the rule to start with:
browse_select 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 Gateway, apply this rule, and every browse_select call is checked against it from then on.
Questions about browse_select
Select an <option> value in a dropdown by @eN ref. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browse_select accepts 3 parameters: ref, value, browser_id. Required: ref, value, browser_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for browse_select: 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 Gateway. Nothing to install.
browse_select 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 browse_select 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 browse_select. 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.
browse_select is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue