Go forward to the next page
AI agents invoke browser_navigate_forward to trigger actions in Playwright MCP. 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 commands are Execute-category tools because they cause the browser to perform an action (advancing to the next page in history) whose side effects depend on context. While navigation itself is relatively benign compared to code execution, it still modifies the browser's state and could be used to navigate to malicious sites or trigger unintended interactions.
From the tool's definition Tool name 'browser_navigate_forward' and description 'Go forward to the next page' indicate an action that triggers browser navigation—an external operation whose effects depend on the current browser state and history.
Attacks that exploit this kind of access
Go forward to the next page. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_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 Playwright MCP. Nothing to install.
browser_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 browser_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 browser_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.
browser_navigate_forward is provided by the Playwright MCP server (markbustamante77/mcp). 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 →