browser_wait · Limetest MCP Server MCP: Risk & Policy

WHAT IT DOES

What browser_wait does on Limetest MCP Server

AI agents invoke browser_wait 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_wait needs a policy

Although superficially passive (waiting), this tool executes a timed operation that progresses automated browser workflows. It is part of an E2E testing framework where an AI agent could misuse timing delays to trigger race conditions, synchronization exploits, or to prolong interactions maliciously.

From the tool's definition Tool performs 'Wait for a specified time in seconds' - an action that triggers external timing operations and affects the execution flow of browser automation workflows, alongside sibling tools like browser_click, browser_drag, and browser_e2e that control…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_wait Rate-limited

browser_wait 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_wait": {
      "limits": [
        {
          "counter": "browser_wait_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_wait

What does the browser_wait tool do? +

Wait for a specified time in seconds. 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_wait? +

Register the Limetest MCP Server MCP server in PolicyLayer and add a rule for browser_wait: 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_wait? +

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

Can I rate-limit browser_wait? +

Yes. Add a rate_limit block to the browser_wait 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_wait completely? +

Set action: deny in the PolicyLayer policy for browser_wait. 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_wait? +

browser_wait 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.