browser_navigate · Wmux MCP: Risk & Policy

WHAT IT DOES

What browser_navigate does on Wmux

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

WHY IT NEEDS A POLICY

Why browser_navigate needs a policy

This tool triggers external operations (browser navigation) whose side effects are determined by the argument (the URL). Navigation can trigger page loads, third-party scripts, tracking, redirects, or malicious content depending on the URL supplied. While not destructive or financial in itself, it is an Execute-category tool because it runs a browser command whose consequences depend on user/agent-supplied input.

From the tool's definition Tool name 'browser_navigate' combined with description 'Navigate the browser page to a URL' indicates execution of a browser action whose effects depend on the URL argument provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_navigate Rate-limited

browser_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": {
    "browser_navigate": {
      "limits": [
        {
          "counter": "browser_navigate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Wmux, so you can run agents against it safely.

FAQ

Questions about browser_navigate

What does the browser_navigate tool do? +

Navigate the browser page to a URL. Returns the final URL after navigation. It is categorised as a Execute tool in the Wmux 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_navigate? +

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

What risk level is browser_navigate? +

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

Can I rate-limit browser_navigate? +

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

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

browser_navigate is provided by the Wmux MCP server (openwong2kim/wmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.