browser_navigate · AutoDev MCP: Risk & Policy

WHAT IT DOES

What browser_navigate does on AutoDev MCP

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

Navigation in a browser can trigger arbitrary external side effects: loading malicious sites, executing scripts on third-party domains, initiating unwanted downloads, or exposing the browser to security risks. However, the blast radius is constrained by the browser session's existing permissions and same-origin policies.

From the tool's definition Tool description states 'Navigate active browser session to target URL' - this performs a navigation action in an active browser context, which is an external operation that triggers browser behavior based on the provided URL argument.

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 AutoDev MCP, so you can run agents against it safely.

FAQ

Questions about browser_navigate

What does the browser_navigate tool do? +

Navigate active browser session to target URL. It is categorised as a Execute tool in the AutoDev MCP 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 AutoDev 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 AutoDev MCP. 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 AutoDev MCP server (rookiejefren/autocoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.