browser_wait

Wait for an element to appear on the page

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/browser-wait.md

WHAT IT DOES

What browser_wait does on CoWork OS

AI agents invoke browser_wait to trigger actions in CoWork OS. 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.

RISK

Why browser_wait is rated High

The tool executes a browser action (waiting/monitoring) that affects the timing and flow of automated interactions. While waiting itself is passive, it's part of an Execute workflow where an agent chains it with other browser actions to accomplish conditional automation.

From the tool's definition Wait for an element to appear on the page — this triggers browser automation that monitors page state and can proceed with subsequent actions based on detection of DOM elements.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_wait safely

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

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.

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

FAQ

Questions about browser_wait

What does the browser_wait tool do? +

Wait for an element to appear on the page. It is categorised as a Execute tool in the CoWork OS 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 CoWork OS 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 CoWork OS. 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 CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS 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 →