High Risk →

go_to_url

Navigate to URL in the current tab. Args: url (str): The URL to navigate to Returns: str: A message confirming navigation

How to control go_to_url ↓

AI agents invoke go_to_url to trigger actions in Mcp Browser Use. 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

Navigating to a URL triggers an external browser action that can load arbitrary web content, initiate network requests, and potentially trigger client-side scripts. This is an active browser operation with side effects beyond simple data retrieval, placing it in the Execute category.

From the tool's definition Navigate to URL in the current tab

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

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

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

go_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 Mcp Browser Use — 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.

Go deeper

What does the go_to_url tool do? +

Navigate to URL in the current tab. Args: url (str): The URL to navigate to Returns: str: A message confirming navigation. It is categorised as a Execute tool in the Mcp Browser Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on go_to_url? +

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

What risk level is go_to_url? +

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

Can I rate-limit go_to_url? +

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

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

go_to_url is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Browser Use tool call.

Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ 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.