Navigate forward in browser history.
AI agents invoke navigate_forward to trigger actions in Selenium MCP Server. 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.
This tool executes a browser navigation operation, which modifies the browser state and can load external web resources. While navigation itself is not inherently destructive or financial, it falls under Execute because it triggers external operations and side effects beyond simple data retrieval.
From the tool's definition Tool 'navigate_forward' navigates forward in browser history, which is an action that triggers external operations (browser state change) whose effects depend on the current browsing context.
Attacks that exploit this kind of access
Navigate forward in browser history. It is categorised as a Execute tool in the Selenium MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Selenium MCP Server MCP server in PolicyLayer and add a rule for navigate_forward: 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 Selenium MCP Server. Nothing to install.
navigate_forward 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_forward 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_forward. 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_forward is provided by the Selenium MCP Server MCP server (nayakprashant/selenium-mcp-server). 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 →