wavexis_select_option
Select an option in a <select> element by value.
This record as markdown: /tools/wavexis-mcp/wavexis-select-option.md
What wavexis_select_option does on Wavexis
AI agents invoke wavexis_select_option to trigger actions in Wavexis. 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 wavexis_select_option is rated High
This tool performs a browser automation action (selecting a dropdown option), which constitutes executing a UI interaction. It can trigger onChange handlers, form submissions, or other side effects depending on the page, making it an Execute-category action. Severity is medium because misuse could trigger unintended form behaviors or state changes in a web application.
From the tool's definition Select an option in a `<select>` element by value — triggers a browser interaction/action on a UI element
Attacks that exploit this kind of access
The rule that runs wavexis_select_option safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_select_option, this is the rule to start with:
wavexis_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 Wavexis, apply this rule, and every wavexis_select_option call is checked against it from then on.
Questions about wavexis_select_option
Select an option in a <select> element by value. It is categorised as a Execute tool in the Wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_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 Wavexis. Nothing to install.
wavexis_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 wavexis_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 wavexis_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.
wavexis_select_option is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
Across the catalogue