// MCP TOOL REFERENCE

wait

Wait for the specified number of seconds. Args: seconds (int, optional): Number of seconds to wait. Defaults to 3. Returns: str: A message confirming the wait

ServerMcp Browser Use
CategoryExecute

How to control wait ↓

WHAT WAIT ON MCP BROWSER USE DOES

AI agents invoke wait to trigger actions in Mcp Browser Use. 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.

THE RISK

High Risk

The wait function executes code (a timer/sleep operation) and could be chained with other browser actions to create timed sequences or timing-based attacks. However, severity is low because the operation has no direct side effects on data or external systems—it merely introduces delays.

From the tool's definition Tool executes a wait/sleep operation with a specified duration. While the operation itself is benign (merely introduces a delay), the ability to execute arbitrary control flow operations that modify timing behavior constitutes execution capability.

Documented attack patterns abuse exactly the kind of access wait gives an agent:

HOW TO CONTROL WAIT

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for wait:

policy.json

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

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.

Create a free account and register Mcp Browser Use — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Mcp Browser Use tools

Execute initialize_browser Initialize a new browser instance. Args: headless: Whether to run browser in h Execute search_google Search the query in Google in the current tab. Args: query (str): The search q Execute click_element Click the element with the specified index. Args: index (int): The index of th Execute go_back Go back to the previous page. Returns: str: A message confirming navigation ba Execute go_to_url Navigate to URL in the current tab. Args: url (str): The URL to navigate to Execute input_text Input text into an interactive element at the specified index. Args: index (in Execute open_tab Open a URL in a new tab. Args: url (str): The URL to open in the new tab R Execute scroll_down Scroll down the page by the specified amount. Args: amount (int, optional): Pi

All 19 Mcp Browser Use tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Mcp Browser Use → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the wait tool do? +

Wait for the specified number of seconds. Args: seconds (int, optional): Number of seconds to wait. Defaults to 3. Returns: str: A message confirming the wait. It is categorised as a Execute tool in the Mcp Browser Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wait? +

Register the Mcp Browser Use MCP server in PolicyLayer and add a rule for 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 Mcp Browser Use. Nothing to install.

What risk level is wait? +

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

Can I rate-limit wait? +

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

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

wait is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Browser Use tool call.

Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP BROWSER USE →

Free to start. No card required.

19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

wait

// WHAT WAIT ON MCP BROWSER USE DOES

// THE RISK

// HOW TO CONTROL WAIT

// EXPLORE