// SCAN REPORT

Ruyipage

34 tools. 20 can modify or destroy data without limits.

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

Last updated: 29 Jun 2026

20 can modify or destroy data

14 read-only

34 tools total

Community server · catalogue entry verified 29/06/2026

How to control Ruyipage ↓

TOOL MAP

What Ruyipage exposes to your agents

Read (14) Write / Execute (20) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Ruyipage tools

Execute · Medium net_headers Modifying request headers affects all subsequent browser network requests, potentially injecting authentication tokens, modifying origin/referer headers, or altering content negotiation. Execute · Medium dom_wait_for This tool executes a waiting/polling operation on a live browser environment, which can trigger side effects depending on page state and timeout behavior. Execute · Critical js_run A tool that runs JavaScript in a browser context is an Execute action with critical severity. Execute · High session_launch Launching a browser session is an Execute action: it triggers an external operation (browser startup) whose side effects depend on arguments (which browser profile, which URLs to load, etc.).

20 of Ruyipage's 34 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Ruyipage

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

Rate limit write operations

{
  "state_save_pdf": {
    "limits": [
      {
        "counter": "state_save_pdf_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "ctx_emulation": {
    "limits": [
      {
        "counter": "ctx_emulation_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 Ruyipage — 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 RUYIPAGE →

Instant setup, no code required.

FULL CATALOGUE

All 34 Ruyipage tools

EXECUTE 19 tools

Execute act_chain act_chain Execute act_click act_click Execute act_input act_input Execute act_simple Perform a simple action on an element. Execute ctx_events ctx_events Execute dom_wait_for Wait for an element to appear on the page. Execute js_preload js_preload Execute js_run js_run Execute nav_back Go back in browser history. Execute nav_forward Go forward in browser history. Execute nav_get Navigate to a URL. Execute nav_refresh Refresh the current page. Execute net_cache Set network cache behavior. Execute net_headers Set or clear extra request headers. Execute net_intercept net_intercept Execute net_listen net_listen Execute session_attach Attach to an already-running Firefox at address. Execute session_auto_attach Auto-detect and attach to a running Firefox / ADS / FlowerBrowser by process signature. Execute session_launch session_launch

WRITE 1 tools

Write state_save_pdf Save the current page as a PDF file.

READ 14 tools

Read ctx_emulation ctx_emulation Read ctx_tabs ctx_tabs Read dom_find dom_find Read dom_find_all Find all matching elements on the page. Read dom_query_in Find a child element inside a previously found element. Read dom_read Read a property from a previously found element. Read dom_release Release an element handle from the registry. Read nav_info Return current page URL, title, and ready state. Read net_collector net_collector Read ruyipage_describe_capabilities Return the current server state: active sessions, element counts, capability switches. Read session_quit session_quit Read state_cookies state_cookies Read state_screenshot state_screenshot Read state_storage state_storage

EXPLORE

Related servers

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

FAQ

Questions about Ruyipage

How do I prevent bulk modifications through Ruyipage? +

The Ruyipage server has 1 write tools including state_save_pdf. 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 Ruyipage.

How many tools does the Ruyipage MCP server expose? +

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

How do I enforce a policy on Ruyipage? +

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

Deterministic rules across all 34 Ruyipage tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RUYIPAGE →

Instant setup, no code required.

34 Ruyipage tools catalogued and risk-classified — across an index of 43,000+ MCP servers.