[LEGACY] Navigate to a URL in an existing browser session. Use navigate_and_scrape instead.
AI agents invoke navigate_to_url to trigger actions in ZMCPTools. 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.
Navigation to arbitrary URLs is an Execute action because it triggers external operations whose effects depend entirely on the URL argument and the target website's behavior.
From the tool's definition Tool description states 'Navigate to a URL in an existing browser session' — this directly performs browser automation that can trigger external side effects (loading arbitrary content, executing scripts, redirects, etc.) based on the URL argument provided.
Documented attack patterns abuse exactly the kind of access navigate_to_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for navigate_to_url:
{
"version": "1",
"default": "deny",
"tools": {
"navigate_to_url": {
"limits": [
{
"counter": "navigate_to_url_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}navigate_to_url 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.
Free to start. No card required.
[LEGACY] Navigate to a URL in an existing browser session. Use navigate_and_scrape instead. It is categorised as a Execute tool in the ZMCPTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for navigate_to_url: 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 ZMCPTools. Nothing to install.
navigate_to_url 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 navigate_to_url 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 navigate_to_url. 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.
navigate_to_url is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.