wait_for_navigation

THE RISK

High Risk

Why wait_for_navigation needs a policy

This tool blocks execution flow until a navigation event completes, which is a form of browser control that can affect the sequence and outcome of automated actions. While not directly destructive or financial, it executes browser operations with side effects (state changes in the browser) and could be misused to trigger unintended page loads or navigation sequences in a compromised browser context.

From the tool's definition Tool controls browser navigation timing and page load states in a Chrome extension. 'Wait for the current page to finish loading' indicates blocking/coordination of browser operations.

Documented attack patterns abuse exactly the kind of access wait_for_navigation gives an agent:

POLICY

How to control wait_for_navigation

PolicyLayer is an MCP gateway — it sits between your AI agents and Webclaw, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_for_navigation:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait_for_navigation": {
      "limits": [
        {
          "counter": "wait_for_navigation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

wait_for_navigation 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.

Create a free account and register Webclaw — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Webclaw tools

Destructive close_tab Close a browser tab Execute drop_files Drop files onto an element (file input or drag-and-drop target) for uploading Execute hover Hover over an element to trigger mouseover events and reveal hidden UI (e.g., dropdown men Execute invoke_webmcp_tool Invoke a WebMCP tool declared by the current page Execute navigate_to Navigate the browser to a URL Execute new_tab Open a new browser tab Execute click Click an element identified by its @ref from the latest page snapshot Execute evaluate Evaluate a JavaScript expression in the page context and return the result.

All 21 Webclaw tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Webclaw → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wait_for_navigation

What does the wait_for_navigation tool do? +

Wait for the current page to finish loading. It is categorised as a Execute tool in the Webclaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wait_for_navigation? +

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

What risk level is wait_for_navigation? +

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

Can I rate-limit wait_for_navigation? +

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

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

wait_for_navigation is provided by the Webclaw MCP server (kuroko1t/webclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Webclaw tool call.

Start from Webclaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →