// SCAN REPORT

Random Web3

10 tools. 9 can modify or destroy data without limits.

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

Last updated: 30 Jun 2026

9 can modify or destroy data

1 read-only

10 tools total

Community server · catalogue entry verified 30/06/2026

How to control Random Web3 ↓

TOOL MAP

What Random Web3 exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Random Web3 tools

Execute · Medium shuffle_array The tool name 'shuffle_array' implies reordering/rearranging array elements. Write · Medium generate_basic_random generate_basic_random Write · Medium generate_distribution generate_distribution Write · Medium generate_random_array generate_random_array

9 of Random Web3's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Random Web3

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

Rate limit write operations

{
  "generate_basic_random": {
    "limits": [
      {
        "counter": "generate_basic_random_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "generate_coordinate": {
    "limits": [
      {
        "counter": "generate_coordinate_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 Random Web3 — 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 RANDOM WEB3 →

Instant setup, no code required.

FULL CATALOGUE

All 10 Random Web3 tools

EXECUTE 1 tools

Execute shuffle_array shuffle_array

WRITE 8 tools

Write generate_basic_random generate_basic_random Write generate_distribution generate_distribution Write generate_random_array generate_random_array Write generate_random_event generate_random_event Write generate_random_feature generate_random_feature Write generate_random_seed generate_random_seed Write generate_random_weighted generate_random_weighted Write generate_rarity generate_rarity

READ 1 tools

Read generate_coordinate generate_coordinate

FAQ

Questions about Random Web3

How do I prevent bulk modifications through Random Web3? +

The Random Web3 server has 8 write tools including generate_basic_random, generate_distribution, generate_random_array. 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 Random Web3.

How many tools does the Random Web3 MCP server expose? +

10 tools across 1 categories: Write. 1 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on Random Web3? +

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

Deterministic rules across all 10 Random Web3 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RANDOM WEB3 →

Instant setup, no code required.

10 Random Web3 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.