browser_navigate_back · Playwright MCP: Risk & Policy

WHAT IT DOES

What browser_navigate_back does on Playwright MCP

AI agents invoke browser_navigate_back to trigger actions in 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.

WHY IT NEEDS A POLICY

Why browser_navigate_back needs a policy

This tool triggers a browser back-navigation action, which executes a state-changing operation on the browser (history traversal). While not destructive or financial, it modifies the current page context and could interfere with agent workflows or application state. It falls under Execute rather than Read because navigation is an action with external effects, not merely data retrieval.

From the tool's definition Tool name 'browser_navigate_back' indicates a browser navigation action that triggers page state changes. Description is empty, but context from sibling tools (browser_click, browser_drag, browser_evaluate) confirms this server provides browser automation…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_navigate_back Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_navigate_back": {
      "limits": [
        {
          "counter": "browser_navigate_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, so you can run agents against it safely.

FAQ

Questions about browser_navigate_back

What does the browser_navigate_back tool do? +

browser_navigate_back. It is categorised as a Execute tool in the Playwright MCP 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_navigate_back? +

Register the 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 Playwright MCP. Nothing to install.

What risk level is browser_navigate_back? +

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

Can I rate-limit browser_navigate_back? +

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.

How do I block browser_navigate_back completely? +

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.

What MCP server provides browser_navigate_back? +

browser_navigate_back is provided by the Playwright MCP server (roshan571/playwright-mcp2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.