browser_select_option · Limetest MCP Server MCP

WHAT IT DOES

What browser_select_option does on Limetest MCP Server

AI agents invoke browser_select_option to trigger actions in Limetest 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 IT NEEDS A POLICY

Why browser_select_option needs a policy

This tool performs a browser interaction (selecting a dropdown option) which constitutes an Execute-level action. It triggers an external browser operation whose effects depend on the arguments provided. While it modifies UI state, the downstream consequences depend heavily on what the dropdown controls (e.g., changing settings, triggering form submissions), making it potentially impactful if misused by an AI agent.

From the tool's definition Select an option in a dropdown — triggers a browser action that changes the state of a UI element

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_select_option Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_select_option": {
      "limits": [
        {
          "counter": "browser_select_option_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Limetest MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_select_option

What does the browser_select_option tool do? +

Select an option in a dropdown. It is categorised as a Execute tool in the Limetest MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_select_option? +

Register the Limetest MCP Server 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 Limetest MCP Server. Nothing to install.

What risk level is browser_select_option? +

browser_select_option is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_select_option? +

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.

How do I block browser_select_option completely? +

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.

What MCP server provides browser_select_option? +

browser_select_option is provided by the Limetest MCP Server MCP server (m2rads/limetest-arch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.