Select option on a <select> by value/label/index using selector or element id.
AI agents invoke select_option to trigger actions in Visual Annotation 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.
This tool performs a browser interaction (selecting a form element option), which is an external operation that triggers UI state changes. It falls under Execute as it drives browser actions whose effects depend on arguments and can trigger downstream operations (form submissions, dynamic page changes).
From the tool's definition Select option on a <select> by value/label/index using selector or element id
Attacks that exploit this kind of access
Select option on a <select> by value/label/index using selector or element id. It is categorised as a Execute tool in the Visual Annotation MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Visual Annotation 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 Visual Annotation MCP. 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 Visual Annotation MCP server (mstocker1/visual_annotation_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 →