browser_history · MCP Playwright Server MCP: Risk & Policy

WHAT IT DOES

What browser_history does on MCP Playwright Server

AI agents invoke browser_history to trigger actions in MCP Playwright 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_history needs a policy

This tool triggers browser navigation actions (back/forward), which are external browser operations whose effects depend on the current browsing context. Navigation can cause page loads, form resubmissions, or state changes, making it an Execute-category action rather than a simple Read.

From the tool's definition Navigate back or forward in browser history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_history Rate-limited

browser_history 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_history": {
      "limits": [
        {
          "counter": "browser_history_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 MCP Playwright Server, so you can run agents against it safely.

FAQ

Questions about browser_history

What does the browser_history tool do? +

Navigate back or forward in browser history. It is categorised as a Execute tool in the MCP Playwright 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_history? +

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

What risk level is browser_history? +

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

Can I rate-limit browser_history? +

Yes. Add a rate_limit block to the browser_history 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_history completely? +

Set action: deny in the PolicyLayer policy for browser_history. 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_history? +

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