browser_localstorage_set · Playwright MCP: Risk & Policy

WHAT IT DOES

What browser_localstorage_set does on Playwright MCP

AI agents use browser_localstorage_set 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_localstorage_set needs a policy

This tool creates or modifies data in the browser's localStorage without explicitly deleting it, making it a Write operation rather than Destructive. The severity is high because localStorage can store sensitive authentication tokens and application state; an agent could maliciously modify critical application data or plant malicious state.

From the tool's definition Tool name 'browser_localstorage_set' directly indicates modification of browser localStorage. The sibling tools include destructive operations like 'browser_cookie_delete' and 'browser_cookie_clear', and write operations like 'browser_cookie_set', positioning…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_localstorage_set Rate-limited

browser_localstorage_set 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_localstorage_set": {
      "limits": [
        {
          "counter": "browser_localstorage_set_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_localstorage_set

What does the browser_localstorage_set tool do? +

browser_localstorage_set. 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_localstorage_set? +

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

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

Can I rate-limit browser_localstorage_set? +

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

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

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