High Risk →

navigate_to

Navigate to a specific URL in a browser tab

How to control navigate_to ↓

What navigate_to does on Pydoll

AI agents invoke navigate_to to trigger actions in Pydoll. 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 needs a policy

Navigate_to executes a browser action with externally-observable side effects (loading a URL, executing page scripts, potential redirects). While not inherently destructive, it can be misused to trigger malicious payloads, phishing flows, or unauthorized API calls.

From the tool's definition Tool performs browser navigation to a specific URL, which triggers external operations (page loads, scripts, redirects) whose effects depend on the URL argument.

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

How to control navigate_to

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "navigate_to": {
      "limits": [
        {
          "counter": "navigate_to_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

navigate_to 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 Pydoll — 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

What does the navigate_to tool do? +

Navigate to a specific URL in a browser tab. It is categorised as a Execute tool in the Pydoll 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? +

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

What risk level is navigate_to? +

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

Can I rate-limit navigate_to? +

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

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

navigate_to is provided by the Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pydoll tool call.

Start from Pydoll, 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.

57 Pydoll 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.