Navigate to URL (Metro bundler, Chrome DevTools, any web page)
AI agents invoke navigate to trigger actions in MCP Connect. 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 URLs is an Execute action because it triggers external operations whose effects are argument-dependent: navigating to a benign page differs vastly from navigating to malicious sites, CSRF endpoints, or local development services. Combined with sibling tools (evaluate_javascript, click_element), this enables arbitrary browser automation workflows.
From the tool's definition Tool navigates to arbitrary URLs via browser automation (Puppeteer), with capability to reach any web page, internal services, or malicious sites. Description explicitly mentions Metro bundler and Chrome DevTools navigation.
Attacks that exploit this kind of access
Navigate to URL (Metro bundler, Chrome DevTools, any web page). It is categorised as a Execute tool in the MCP Connect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Connect 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 MCP Connect. 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 MCP Connect MCP server (plaintest/mcp-connect). 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 →