select-option
A execute tool on the AdsPower LocalAPI MCP server.
This record as markdown: /tools/adspower-adspower-browser/select-option.md
What select-option does on AdsPower LocalAPI MCP Server
AI agents invoke select-option to trigger actions in AdsPower LocalAPI MCP Server. 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 select-option is rated High
Given the server context (browser automation via AdsPower LocalAPI) and sibling tools like 'click-element', 'select-option' most likely performs a browser UI interaction (selecting a dropdown/option element), which is an Execute-category action. Confidence is low due to empty description.
From the tool's definition Tool name 'select-option' with empty description; inferred from sibling tools like 'click-element' and 'connect-browser-with-ws' that this server performs browser automation actions.
Attacks that exploit this kind of access
The rule that runs select-option safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdsPower LocalAPI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For select-option, this is the rule to start with:
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 AdsPower LocalAPI MCP Server, apply this rule, and every select-option call is checked against it from then on.
Questions about select-option
select-option is a execute tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Execute tool in the AdsPower LocalAPI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for 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 AdsPower LocalAPI MCP Server. Nothing to install.
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 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 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.
select-option is provided by the AdsPower LocalAPI MCP Server MCP server (adspower/adspower-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdsPower LocalAPI MCP Server, and thousands of servers like it.
Across the catalogue