navigate
AI agents invoke navigate to trigger actions in WebControl. 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.
Navigate on a browser automation platform is an Execute action: it triggers external operations (page loads, script execution, network requests) whose effects depend on the target URL and page behavior. While it doesn't directly delete data (Destructive) or move money (Financial), it can load malicious pages, trigger unintended actions through form fills and clicks, or execute JavaScript with side effects.
From the tool's definition Tool named 'navigate' on a headless browser automation server that 'enables navigating pages, filling forms, and executing JavaScript.' The sibling tools (click, execute_js, fill) confirm this is a browser control interface.
Attacks that exploit this kind of access
navigate. It is categorised as a Execute tool in the WebControl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WebControl MCP server in PolicyLayer and add a rule for 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 WebControl. Nothing to install.
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 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 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.
navigate is provided by the WebControl MCP server (matansht/webcontrol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →