AI agents invoke scout_navigate to trigger actions in Scout. 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.
While the tool itself is relatively constrained (it navigates and returns metadata), it falls into Execute rather than Read because: (1) navigation is an action that changes browser state and can trigger side effects on remote servers, (2) the URL parameter is attacker-controlled, and (3) the optional snapshot feature can read sensitive page content.
From the tool's definition 'Navigate to a URL' and the context that this is a 'Browser MCP server that connects to your existing browser' enabling 'AI agents to interact with web pages.' Navigation with optional snapshot collection is an Execute action that triggers external browser…
Attacks that exploit this kind of access
Navigate to a URL. Returns {url, title} by default (lean). Set snapshot=true for full accessibility tree + screenshot (expensive — use only when you need to discover page structure). It is categorised as a Execute tool in the Scout MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Scout MCP server in PolicyLayer and add a rule for scout_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 Scout. Nothing to install.
scout_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 scout_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 scout_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.
scout_navigate is provided by the Scout MCP server (lautrek/scout). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
scout_navigate is one line of Scout's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →