browse_navigate

Navigate an open session to a URL (SSRF-guarded). Returns url/status/title + any anti-bot challenge. Free.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

High RISK CLASS

Category Execute

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse-navigate.md

WHAT IT DOES

What browse_navigate does on Gateway

AI agents invoke browse_navigate to trigger actions in Gateway. 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.

Parameter	Type	Required	Description
`url`	string	Yes	the page to load (http/https)
`browser_id`	string	Yes	from browse_open

Parameters from the server's own tool schema.

RISK

Why browse_navigate is rated High

This tool performs an active browser navigation action to an arbitrary URL, which constitutes executing an external operation. Despite the SSRF guard, it triggers real HTTP requests to attacker-controlled destinations, can be used to probe internal services, interact with external systems, or exfiltrate data via side channels.

From the tool's definition Navigate an open session to a URL (SSRF-guarded). Returns url/status/title + any anti-bot challenge.

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browse_navigate safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_navigate, this is the rule to start with:

browse_navigate Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every browse_navigate call is checked against it from then on.

FAQ

Questions about browse_navigate

What does the browse_navigate tool do? +

Navigate an open session to a URL (SSRF-guarded). Returns url/status/title + any anti-bot challenge. Free. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does browse_navigate accept? +

browse_navigate accepts 2 parameters: url, browser_id. Required: url, browser_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browse_navigate? +

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

What risk level is browse_navigate? +

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

Can I rate-limit browse_navigate? +

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

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

browse_navigate is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools → High-risk tools on this server →

Across the catalogue

browser_navigate on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →