// SCAN REPORT

Ruishu MCP

3 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 11 Jun 2026

2 can modify or destroy data

1 read-only

3 tools total

Community server · catalogue entry verified 11/06/2026

How to control Ruishu MCP ↓

TOOL MAP

Read (1) Write / Execute (2) Destructive / Financial (0)

MOST DANGEROUS TOOLS

High Risk

Execute · High execute_page_action This tool enables execution of arbitrary JavaScript within a browser page context. Execute · High init_ruishu_hook This tool initializes a system-level hook into a browser environment using Chrome DevTools Protocol, binding probes and manipulating ServiceWorker/caching layers.

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

HOW TO CONTROL RUISHU MCP

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

Cap read operations

{
  "get_intercepted_traffic": {
    "limits": [
      {
        "counter": "get_intercepted_traffic_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 Ruishu MCP — 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 RUISHU →

Free to start. No card required.

ALL 3 RUISHU MCP TOOLS

EXECUTE 2 tools

Execute execute_page_action Auxiliary action: allows executing specified JS in the page (simulate click/scroll/input, etc.) to trigger req Execute init_ruishu_hook Step 1: Pipeline Initialization. Binds the system-level probe to the target environment to extract high-qualit

READ 1 tools

Read get_intercepted_traffic Step 2: Data Observation. Retrieves the merged high-fidelity JSON log datasets processed by the data pipeline.

RELATED SERVERS

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

FAQ

Is the Ruishu MCP server safe to use without restrictions? +

The Ruishu MCP server is primarily read-only with 1 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Ruishu MCP server expose? +

3 tools across 2 categories: Execute, Read. 1 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Ruishu MCP? +

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

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

ENFORCE POLICY ON RUISHU →

Free to start. No card required.

3 Ruishu MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Ruishu MCP

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL RUISHU MCP

// ALL 3 RUISHU MCP TOOLS

// RELATED SERVERS

// FAQ