browser_navigate
Navigate to a URL. Opens the browser if not already running. Only http: and https: URLs are accepted (plus the special about:blank). Other URL schemes (file:, chrome:, chrome-extension:, javascript:, data:, view-source:, about:*) are refused. IMPORTANT: After navigating, call browser_snapshot to ...
This record as markdown: /tools/freshdesk/browser-navigate.md
What browser_navigate does on Freshdesk
AI agents invoke browser_navigate to trigger actions in Freshdesk. 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 with side effects (opening browser, loading pages, triggering network requests). While restricted to http/https schemes (mitigating some risk), it still constitutes an Execute category action because it triggers external operations whose outcomes depend on user-supplied arguments.
From the tool's definition Tool name 'browser_navigate' combined with description 'Navigate to a URL. Opens the browser if not already running.' indicates execution of browser navigation actions, which trigger external operations (browser state changes, network requests, page loads)…
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 Freshdesk, 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 Freshdesk, apply this rule, and every browser_navigate call is checked against it from then on.
Questions about browser_navigate
Navigate to a URL. Opens the browser if not already running. Only http: and https: URLs are accepted (plus the special about:blank). Other URL schemes (file:, chrome:, chrome-extension:, javascript:, data:, view-source:, about:*) are refused. IMPORTANT: After navigating, call browser_snapshot to see the page content before interacting. It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Freshdesk 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 Freshdesk. 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 Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
Across the catalogue