Navigate forward in browser history.
AI agents invoke browser_forward to trigger actions in Daytona 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 history), which is an external operation that causes a state change in the browser. It falls under Execute as it performs a browser action, though its blast radius is low since it only navigates to a previously visited page.
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 Daytona Playwright MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Daytona Playwright MCP Server MCP server in PolicyLayer and add a rule for browser_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 Daytona Playwright MCP Server. Nothing to install.
browser_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_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_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_forward is provided by the Daytona Playwright MCP Server MCP server (jamesmurdza/playwright-daytona-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 →