Go back to the previous page. Returns: str: A message confirming navigation back
AI agents invoke go_back to trigger actions in Mcp Browser Use. 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 performs a browser navigation action (equivalent to pressing the browser back button), which is an external operation that changes the browser state. It fits the Execute category as it triggers a browser action. Severity is medium because navigating back could disrupt multi-step workflows or cause loss of form data, but it is generally reversible by navigating forward again.
From the tool's definition Go back to the previous page — triggers a browser navigation action
Documented attack patterns abuse exactly the kind of access go_back gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for go_back:
{
"version": "1",
"default": "deny",
"tools": {
"go_back": {
"limits": [
{
"counter": "go_back_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} go_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. Returns: str: A message confirming navigation back. It is categorised as a Execute tool in the Mcp Browser Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Browser Use MCP server in PolicyLayer and add a rule for go_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 Mcp Browser Use. Nothing to install.
go_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 go_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 go_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.
go_back is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ MCP servers.