Reset MCP-side browser residual state without closing the browser. Args: clear_persistent_hooks: Remove all persistent init scripts. clear_network_capture: Clear network request buffer and stop captures. clear_active_routes: Clear instrumentation routes. clear_cookies: ALSO clear browser cookies ...
AI agents call reset_browser_state to permanently remove resources in Camoufox Reverse — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While some actions are reversible (clearing buffers, stopping captures), the tool explicitly labels cookie clearing as 'destructive' and also supports clearing localStorage/sessionStorage — both of which irreversibly remove stored data. Since the most severe applicable category wins and the tool can irrecoverably wipe browser-side persistent state (cookies, storage), Destructive is the correct classification.
From the tool's definition 'Reset MCP-side browser residual state', 'Remove all persistent init scripts', 'Clear network request buffer and stop captures', 'clear browser cookies (destructive; default False)', 'clear localStorage/sessionStorage'
Documented attack patterns abuse exactly the kind of access reset_browser_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 reset_browser_state:
{
"version": "1",
"default": "deny",
"hide": [
"reset_browser_state"
]
}reset_browser_state disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Reset MCP-side browser residual state without closing the browser. Args: clear_persistent_hooks: Remove all persistent init scripts. clear_network_capture: Clear network request buffer and stop captures. clear_active_routes: Clear instrumentation routes. clear_cookies: ALSO clear browser cookies (destructive; default False). clear_storage: ALSO clear localStorage/sessionStorage (default False). It is categorised as a Destructive tool in the Camoufox Reverse MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Camoufox Reverse MCP server in PolicyLayer and add a rule for reset_browser_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.
reset_browser_state is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_browser_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 reset_browser_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.
reset_browser_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.