browser_wait_until_stable

A execute tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

High RISK CLASS

Category Execute

Parameters 20 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-until-stable.md

WHAT IT DOES

What browser_wait_until_stable does on Looking Glass

AI agents invoke browser_wait_until_stable 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	—	Max wait time in ms (default: 15000)
`checkSpinners`	boolean	—	Check for loading spinners (default: true)

Parameters from the server's own tool schema.

RISK

Why browser_wait_until_stable is rated High

The tool triggers browser state transitions and waits for stability conditions—a control operation on an external system. While non-destructive and non-financial, it executes agent-directed browser behavior whose effects depend on the browser's current state and pending operations.

From the tool's definition Tool name 'browser_wait_until_stable' indicates triggering browser actions. Context shows this is part of a 72-tool browser automation suite ('AI-native browser for agents').

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_wait_until_stable 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_until_stable, this is the rule to start with:

browser_wait_until_stable Rate-limited

browser_wait_until_stable 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_until_stable": {
      "limits": [
        {
          "counter": "browser_wait_until_stable_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_until_stable call is checked against it from then on.

FAQ

Questions about browser_wait_until_stable

What does the browser_wait_until_stable tool do? +

browser_wait_until_stable 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_until_stable accept? +

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

How do I enforce a policy on browser_wait_until_stable? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_wait_until_stable: 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_until_stable? +

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

Can I rate-limit browser_wait_until_stable? +

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

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

browser_wait_until_stable 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 →