Navigate forward in browser history
AI agents invoke playwright_go_forward to trigger actions in Playwright 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 triggers a browser navigation action (moving forward in browser history), which is an external operation that causes the browser to load a new page. It falls under Execute as it performs a browser action whose effects depend on the current state of the browser session. It's not purely Read since it changes the browser state, and not Write/Destructive as it doesn't modify or delete data directly.
From the tool's definition Navigate forward in browser history
Attacks that exploit this kind of access
Navigate forward in browser history. It is categorised as a Execute tool in the Playwright MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for playwright_go_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 Server. Nothing to install.
playwright_go_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 playwright_go_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 playwright_go_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.
playwright_go_forward is provided by the Playwright MCP Server MCP server (vinothbhc1986/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 →