browse_wait_for

Wait for a CSS selector to appear on the current page (for async/SPA pages after a click or navigate, before you snapshot/act). Returns ok once present, else an honest timeout.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

High RISK CLASS

Category Execute

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse-wait-for.md

WHAT IT DOES

What browse_wait_for does on Gateway

AI agents invoke browse_wait_for to trigger actions in Gateway. 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
`selector`	string	Yes	CSS selector to wait for
`browser_id`	string	Yes	from browse_open
`timeout_ms`	integer	—	max wait (default 8000)

Parameters from the server's own tool schema.

RISK

Why browse_wait_for is rated High

This tool interacts with a live browser session, waiting for DOM elements to appear. It is part of a browser automation workflow (alongside click/navigate actions), making it an Execute-category tool — it triggers and coordinates browser-side operations. While it doesn't directly execute code, it gates and enables further browser actions, and misuse could facilitate manipulation of web sessions.

From the tool's definition 'Wait for a CSS selector to appear on the current page (for async/SPA pages after a click or navigate, before you snapshot/act)'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browse_wait_for safely

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

browse_wait_for Rate-limited

browse_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": {
    "browse_wait_for": {
      "limits": [
        {
          "counter": "browse_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 Gateway, apply this rule, and every browse_wait_for call is checked against it from then on.

FAQ

Questions about browse_wait_for

What does the browse_wait_for tool do? +

Wait for a CSS selector to appear on the current page (for async/SPA pages after a click or navigate, before you snapshot/act). Returns ok once present, else an honest timeout. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does browse_wait_for accept? +

browse_wait_for accepts 3 parameters: selector, browser_id, timeout_ms. Required: selector, browser_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browse_wait_for? +

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

What risk level is browse_wait_for? +

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

Can I rate-limit browse_wait_for? +

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

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

browse_wait_for is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway 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 →