browser_navigate
Navigate to URL or go back/forward/reload
This record as markdown: /tools/alexgladkov-claude-in-mobile/browser-navigate.md
What browser_navigate does on Claude Mobile
AI agents invoke browser_navigate to trigger actions in Claude Mobile. 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 browser_navigate is rated High
This tool executes browser navigation commands that can load arbitrary content, trigger external services, and execute client-side code. While not destructive by itself, it has broad potential impact on device state and can facilitate further attacks.
From the tool's definition 'Navigate to URL' and 'go back/forward/reload' are browser control actions that trigger external operations (network requests, page loads, JavaScript execution) whose effects depend on the URL argument provided.
Attacks that exploit this kind of access
The rule that runs browser_navigate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_navigate, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every browser_navigate call is checked against it from then on.
Questions about browser_navigate
Navigate to URL or go back/forward/reload. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile 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 Claude Mobile. Nothing to install.
browser_navigate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
browser_navigate is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue