browser_wait_for

A execute tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

High RISK CLASS

Category Execute

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-wait-for.md

WHAT IT DOES

What browser_wait_for does on Looking Glass

AI agents invoke browser_wait_for to trigger actions in Looking Glass. 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.

Parameter	Type	Required	Description
`timeout`	number	—	Timeout in ms (default: 15000)
`condition`	string	Yes	What to wait for (e.g. "search results loaded", "spinner disappears", "URL contains /dashboard")

Parameters from the server's own tool schema.

RISK

Why browser_wait_for is rated High

This tool performs a browser action (waiting for conditions to be met) whose effects depend on arguments and runtime state. While the description is empty, the naming convention and server context (AI-native browser for agents) establish this as an Execute-category tool. It does not retrieve data (Read), modify reversibly (Write), delete (Destructive), or move money (Financial).

From the tool's definition Tool name 'browser_wait_for' combined with sibling tools like 'browser_click', 'browser_action_history', and 'browser_analyze_page' indicates this is a browser automation tool that triggers external operations (waiting for page elements, navigation, or…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_wait_for safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_wait_for, this is the rule to start with:

browser_wait_for Rate-limited

browser_wait_for 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_for": {
      "limits": [
        {
          "counter": "browser_wait_for_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every browser_wait_for call is checked against it from then on.

FAQ

Questions about browser_wait_for

What does the browser_wait_for tool do? +

browser_wait_for is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does browser_wait_for accept? +

browser_wait_for accepts 2 parameters: timeout, condition. Required: condition. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_wait_for? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_wait_for: 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 Looking Glass. Nothing to install.

What risk level is browser_wait_for? +

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

Can I rate-limit browser_wait_for? +

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

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

browser_wait_for is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Looking Glass, and thousands of servers like it.

This server

All 71 Looking Glass tools → High-risk tools on this server →

Across the catalogue

browser_wait_for_element on Percepta MCP Server →wait_for_renders on Why Did You Render →qt_wait_for on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →