Save cookies + localStorage to a JSON file. Reload via storage_state_load on a fresh browser to skip login/CF entirely.
AI agents use storage_state_save to create or update resources in MCP Camoufox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Camoufox environment.
This tool creates and persists authentication and session data (cookies, localStorage) to files. While not destructive (data can be overwritten), it modifies stored state for later reuse. The 'high' severity reflects the security risk: saved credentials and session tokens could be exfiltrated or replayed by an attacker, enabling account takeover or unauthorized access to third-party services.
From the tool's definition "Save cookies + localStorage to a JSON file" - creates and writes persistent state data. The description explicitly confirms write operations to durable storage.
Documented attack patterns abuse exactly the kind of access storage_state_save gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for storage_state_save:
{
"version": "1",
"default": "deny",
"tools": {
"storage_state_save": {
"limits": [
{
"counter": "storage_state_save_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}storage_state_save 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.
Save cookies + localStorage to a JSON file. Reload via storage_state_load on a fresh browser to skip login/CF entirely. It is categorised as a Write tool in the MCP Camoufox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for storage_state_save: 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 Camoufox. Nothing to install.
storage_state_save 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 storage_state_save 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 storage_state_save. 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.
storage_state_save is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Camoufox, 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.
102 MCP Camoufox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.