// SCAN REPORT

Camoufox Reverse

36 tools. 18 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

18 can modify or destroy data

18 read-only

36 tools total

Community server · catalogue entry verified 11/06/2026

How to control Camoufox Reverse ↓

TOOL MAP

Read (18) Write / Execute (16) Destructive / Financial (2)

MOST DANGEROUS TOOLS

Critical Risk

Destructive · Medium reset_browser_state 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 rem Destructive · High remove_hooks Remove installed hooks and restore original objects in-place. Args: keep_persistent: If True, keep persistent init_scripts regi Execute · High launch_browser Launching a browser is an Execute-category action because it triggers external operations (browser automation) whose effects depend on subsequent arguments and user interaction. Execute · High navigate Navigate in a browser context executes the action of loading a URL, which triggers external operations whose effects depend on the target argument.

18 of Camoufox Reverse's 36 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL CAMOUFOX REVERSE

PolicyLayer is an MCP gateway — it sits between your AI agents and Camoufox Reverse, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "remove_hooks": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "close_browser": {
    "limits": [
      {
        "counter": "close_browser_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_cookie_sources": {
    "limits": [
      {
        "counter": "analyze_cookie_sources_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Camoufox Reverse — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CAMOUFOX REVERSE →

Free to start. No card required.

ALL 36 CAMOUFOX REVERSE TOOLS

DESTRUCTIVE 2 tools

Destructive remove_hooks Remove installed hooks and restore original objects in-place. Args: keep_persistent: If True, kee Destructive reset_browser_state Reset MCP-side browser residual state without closing the browser. Args: clear_persistent_hooks:

EXECUTE 13 tools

Execute launch_browser launch_browser Execute navigate navigate Execute wait_for Wait for an element to appear or a network request matching a URL pattern. Execute evaluate_js evaluate_js Execute hook_function hook_function Execute hook_jsvmp_interpreter hook_jsvmp_interpreter Execute inject_hook_preset inject_hook_preset Execute intercept_request intercept_request Execute reload Reload the current page, preserving any init scripts. Execute trace_property_access trace_property_access Execute verify_signer_offline Offline verify a signing function against user-provided samples. Typical workflow: 1. Capture real Execute click Click on a page element. Execute type_text Type text into an input field with realistic keystroke delays.

WRITE 3 tools

Write close_browser Close the Camoufox browser and release all resources. Write export_state Export the complete browser state (cookies + storage) to a JSON file. Args: save_path: Local file Write import_state Import browser state from a JSON file by creating a new context. Args: state_path: Path to the st

READ 18 tools

Read analyze_cookie_sources analyze_cookie_sources Read check_environment One-stop self-check of MCP environment, dependencies, and browser state. v1.0.0: session-related checks r Read compare_env Collect browser environment fingerprint data for comparison with Node.js/jsdom. Args: properties: Read cookies cookies Read get_console_logs get_console_logs Read get_network_request Get full details of a specific captured network request. Args: request_id: The ID of the request Read get_page_info Get current page URL, title, and viewport size. Read get_request_initiator get_request_initiator Read get_storage get_storage Read instrumentation instrumentation Read list_network_requests list_network_requests Read list_trace_files List all trace files on disk (for post-hoc analysis). Returns: dict with traces_dir, total file c Read network_capture network_capture Read query_trace_file Query a specific historical trace file (post-hoc analysis). Args: file_path: Path to the .jsonl t Read scripts scripts Read search_code search_code Read take_screenshot Take a screenshot of the current page or a specific element. Args: full_page: Capture the entire Read take_snapshot Get the accessibility tree of the current page (token-efficient).

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Can an AI agent delete data through the Camoufox Reverse MCP server? +

Yes. The Camoufox Reverse server exposes 2 destructive tools including remove_hooks, reset_browser_state. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Camoufox Reverse? +

The Camoufox Reverse server has 3 write tools including close_browser, export_state, import_state. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Camoufox Reverse.

How many tools does the Camoufox Reverse MCP server expose? +

36 tools across 4 categories: Destructive, Execute, Read, Write. 18 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on Camoufox Reverse? +

Register the Camoufox Reverse MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Camoufox Reverse tool call.

Deterministic rules across all 36 Camoufox Reverse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CAMOUFOX REVERSE →

Free to start. No card required.

36 Camoufox Reverse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Camoufox Reverse

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL CAMOUFOX REVERSE

// ALL 36 CAMOUFOX REVERSE TOOLS

// RELATED SERVERS

// FAQ