Navigate the browser to a URL and wait for DOM content to load. Use when the user wants to go to a specific webpage, URL, or link. For read tasks (
AI agents invoke pilot_navigate to trigger actions in Pilot. 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 is not a simple data retrieval (Read). While superficially passive, browser navigation in Playwright is an Execute operation: it loads and runs code from remote servers, can trigger side effects through JavaScript execution, and the consequences depend entirely on which URL is provided.
From the tool's definition Tool performs browser navigation via Playwright, a browser automation framework. The description states it 'Navigate[s] the browser to a URL and wait[s] for DOM content to load.' Browser automation that navigates to arbitrary URLs can trigger network…
Documented attack patterns abuse exactly the kind of access pilot_navigate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for pilot_navigate:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_navigate": {
"limits": [
{
"counter": "pilot_navigate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} pilot_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.
Free to start. No card required.
Navigate the browser to a URL and wait for DOM content to load. Use when the user wants to go to a specific webpage, URL, or link. For read tasks (. It is categorised as a Execute tool in the Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_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 Pilot. Nothing to install.
pilot_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 pilot_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 pilot_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.
pilot_navigate is provided by the Pilot MCP server (tacosyhorchata/pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 61 Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
61 Pilot tools catalogued and risk-classified — across an index of 42,500+ MCP servers.