browser_wait_for_navigation

THE RISK

High Risk

Why browser_wait_for_navigation needs a policy

This tool controls browser behavior by waiting for navigation completion, which is a form of browser automation/execution. While it doesn't directly modify data or trigger financial transactions, it enables orchestration of browser actions whose effects depend on the navigation URL and resulting page state.

From the tool's definition Tool name 'browser_wait_for_navigation' combined with description 'Wait for page navigation to complete' indicates triggering or blocking on browser navigation events.

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

POLICY

How to control browser_wait_for_navigation

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

policy.json

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

browser_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 Concurrent Browser MCP — 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 Concurrent Browser MCP tools

Destructive browser_close_all_instances Close all browser instances Destructive browser_close_instance Close the specified browser instance Execute browser_evaluate Execute JavaScript code in the page context Execute browser_navigate Navigate to a specified URL Execute browser_wait_for_element Wait for an element to appear Execute browser_click Click on a page element Execute browser_create_instance Create a new browser instance Execute browser_fill Fill a form field

All 20 Concurrent Browser MCP 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 Concurrent Browser MCP → 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 browser_wait_for_navigation

What does the browser_wait_for_navigation tool do? +

Wait for page navigation to complete. It is categorised as a Execute tool in the Concurrent Browser MCP 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_navigation? +

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

What risk level is browser_wait_for_navigation? +

browser_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 browser_wait_for_navigation? +

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

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

browser_wait_for_navigation is provided by the Concurrent Browser MCP server (sailaoda/concurrent-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Concurrent Browser MCP tool call.

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

CHECK YOUR STACK →