browser_storage_state · Playwright MCP: Risk & Policy

WHAT IT DOES

What browser_storage_state does on Playwright MCP

AI agents use browser_storage_state to create or update resources in Playwright MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright MCP environment.

WHY IT NEEDS A POLICY

Why browser_storage_state needs a policy

An AI agent can call browser_storage_state faster than any human can review — one bad instruction and it creates or modifies resources in Playwright MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_storage_state Rate-limited

browser_storage_state stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_storage_state": {
      "limits": [
        {
          "counter": "browser_storage_state_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_storage_state

What does the browser_storage_state tool do? +

browser_storage_state. It is categorised as a Write tool in the Playwright MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_storage_state? +

Register the Playwright MCP server in PolicyLayer and add a rule for browser_storage_state: 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_storage_state? +

browser_storage_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_storage_state? +

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

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

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