AI agents invoke browser_navigate_back to trigger actions in Better 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 actions fall under Execute category because they trigger external operations (browser state changes, potential page loads, script execution on target page) whose outcomes depend on runtime context. While not destructive or modifying persistent data, the action executes browser commands that can have side effects (triggering page load handlers, executing onload scripts, changing application state).
From the tool's definition Tool performs browser navigation action ('Go back to the previous page'), which alters the runtime state of the browser by triggering page transitions. This is an external operation whose effects depend on browser history context.
Documented attack patterns abuse exactly the kind of access browser_navigate_back gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Better Playwright MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_navigate_back:
{
"version": "1",
"default": "deny",
"tools": {
"browser_navigate_back": {
"limits": [
{
"counter": "browser_navigate_back_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_navigate_back stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Go back to the previous page. It is categorised as a Execute tool in the Better Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Better Playwright MCP server in PolicyLayer and add a rule for browser_navigate_back: 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 Better Playwright MCP. Nothing to install.
browser_navigate_back 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_back 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_back. 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_back is provided by the Better Playwright MCP server (livoras/better-playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Better Playwright MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Better Playwright MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.