browser_wait_for · Scrapeless MCP: Risk & Policy

WHAT IT DOES

What browser_wait_for does on Scrapeless

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

WHY IT NEEDS A POLICY

Why browser_wait_for needs a policy

This tool executes a browser operation (waiting for an element) whose effects depend on the CSS selector argument and current page state. While it does not directly modify data or execute arbitrary code, it is a browser automation primitive that triggers external operations and would be misused by an AI agent to navigate, wait for, and interact with web pages in unintended ways.

From the tool's definition Tool name 'browser_wait_for' and description 'Wait for a specific page element to appear' indicates triggering browser actions that depend on external page state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Scrapeless, so you can run agents against it safely.

FAQ

Questions about browser_wait_for

What does the browser_wait_for tool do? +

Wait for a specific page element to appear. Restrictions: Requires a valid CSS selector for the element to wait for. Valid: Wait for the element. It is categorised as a Execute tool in the Scrapeless 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_for? +

Register the Scrapeless 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 Scrapeless. 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 Scrapeless MCP server (scrapeless-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.