JS Reverse MCP

22 tools. 11 can modify or destroy data without limits.

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

Last updated:

11 can modify or destroy data
11 read-only
22 tools total

Community server · catalogue entry verified 26/06/2026

How to control JS Reverse MCP ↓

What JS Reverse MCP exposes to your agents

Read (11) Write / Execute (9) Destructive / Financial (2)
Critical Risk

The most dangerous JS Reverse MCP tools

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

How to control JS Reverse MCP

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

Deny destructive operations
{
  "clear_site_data": {
    "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
{
  "save_script_source": {
    "limits": [
      {
        "counter": "save_script_source_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_paused_info": {
    "limits": [
      {
        "counter": "get_paused_info_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register JS Reverse MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON JS REVERSE →

Instant setup, no code required.

All 22 JS Reverse MCP tools

Related servers

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

Questions about JS Reverse MCP

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

Yes. The JS Reverse MCP server exposes 2 destructive tools including clear_site_data, remove_breakpoint. 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 JS Reverse MCP? +

The JS Reverse MCP server has 2 write tools including save_script_source, select_frame. 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 JS Reverse MCP.

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

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

How do I enforce a policy on JS Reverse MCP? +

Register the JS 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 JS Reverse MCP tool call.

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

Instant setup, no code required.

22 JS Reverse MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.