AI agents use browser_set_storage_state to create or update resources in Playwright — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright environment.
The tool modifies browser storage state, which is reversible but affects how the browser and web applications behave. This is a Write operation rather than Read (it sets rather than gets), and does not delete data (so not Destructive). While it enables browser automation, it itself does not execute arbitrary code or trigger external operations (Execute category).
From the tool's definition Tool name contains 'set_storage_state' indicating it modifies browser storage (localStorage, sessionStorage, or similar state).
Documented attack patterns abuse exactly the kind of access browser_set_storage_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_set_storage_state:
{
"version": "1",
"default": "deny",
"tools": {
"browser_set_storage_state": {
"limits": [
{
"counter": "browser_set_storage_state_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}browser_set_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.
Free to start. No card required.
browser_set_storage_state. It is categorised as a Write tool in the Playwright MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_set_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. Nothing to install.
browser_set_storage_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the browser_set_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.
Set action: deny in the PolicyLayer policy for browser_set_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.
browser_set_storage_state is provided by the Playwright MCP server (@playwright/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
68 Playwright tools catalogued and risk-classified — across an index of 43,000+ MCP servers.