Export the complete browser state (cookies + storage) to a JSON file. Args: save_path: Local file path to save the state JSON. Returns: dict with status and the save path.
AI agents use export_state to create or update resources in Camoufox Reverse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Camoufox Reverse environment.
This tool writes browser state data (cookies and storage) to a file on the local filesystem. It creates/overwrites a file at the specified path. This is a Write operation — it does not delete data, execute code, or involve financial transactions, but it does create a file with potentially sensitive session data (cookies).
From the tool's definition Export the complete browser state (cookies + storage) to a JSON file... Local file path to save the state JSON
Documented attack patterns abuse exactly the kind of access export_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camoufox Reverse, and nothing reaches the server without passing your rules. This is the rule we recommend for export_state:
{
"version": "1",
"default": "deny",
"tools": {
"export_state": {
"limits": [
{
"counter": "export_state_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_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.
Export the complete browser state (cookies + storage) to a JSON file. Args: save_path: Local file path to save the state JSON. Returns: dict with status and the save path. It is categorised as a Write tool in the Camoufox Reverse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Camoufox Reverse MCP server in PolicyLayer and add a rule for export_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 Camoufox Reverse. Nothing to install.
export_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 export_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 export_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.
export_state is provided by the Camoufox Reverse MCP server (whitenightshadow/camoufox-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Camoufox Reverse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Camoufox Reverse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.