browser_go_back · Playwright MCP Server MCP: Risk & Policy

WHAT IT DOES

What browser_go_back does on Playwright MCP Server

AI agents invoke browser_go_back 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.

WHY IT NEEDS A POLICY

Why browser_go_back needs a policy

Navigating back in browser history is a browser action that modifies the current state of the browser session (current URL, page content, form state). It is not a pure read operation as it causes side effects in the browser environment. It falls under Execute as it triggers an external browser operation whose effects depend on the current navigation history.

From the tool's definition 'Go back in browser history' — triggers a browser navigation action that changes the state of the browser session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_go_back Rate-limited

browser_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_go_back": {
      "limits": [
        {
          "counter": "browser_go_back_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Playwright MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_go_back

What does the browser_go_back tool do? +

Go back 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.

How do I enforce a policy on browser_go_back? +

Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for browser_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 Playwright MCP Server. Nothing to install.

What risk level is browser_go_back? +

browser_go_back is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_go_back? +

Yes. Add a rate_limit block to the browser_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.

How do I block browser_go_back completely? +

Set action: deny in the PolicyLayer policy for browser_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.

What MCP server provides browser_go_back? +

browser_go_back is provided by the Playwright MCP Server MCP server (nolecram/build_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.