High Risk →

navigate-to-url

Navigate the active browser to a specified URL

How to control navigate-to-url ↓

What navigate-to-url does on WDIO MCP Server

AI agents invoke navigate-to-url to trigger actions in WDIO MCP Server. 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.

High Risk

Why navigate-to-url needs a policy

This tool triggers external network operations and can cause the browser to load arbitrary URLs, potentially leading to unintended consequences such as accessing malicious sites, triggering undesired server requests, or inducing side effects through the loaded page content.

From the tool's definition Tool performs browser navigation action 'Navigate the active browser to a specified URL' which executes external operations (HTTP requests, page loads) whose effects depend on the URL argument provided.

Documented attack patterns abuse exactly the kind of access navigate-to-url gives an agent:

How to control navigate-to-url

PolicyLayer is an MCP gateway — it sits between your AI agents and WDIO MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for navigate-to-url:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "navigate-to-url": {
      "limits": [
        {
          "counter": "navigate-to-url_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

navigate-to-url 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.

  1. Create a free account and register WDIO MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about navigate-to-url

What does the navigate-to-url tool do? +

Navigate the active browser to a specified URL. It is categorised as a Execute tool in the WDIO MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate-to-url? +

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

What risk level is navigate-to-url? +

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

Can I rate-limit navigate-to-url? +

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

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

navigate-to-url is provided by the WDIO MCP Server MCP server (siri100/wdio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WDIO MCP Server tool call.

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

Free to start. No card required.

7 WDIO MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.