Crypto_MCP

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

1 write tool that can modify data. Rate limits recommended.

Last updated:

2 can modify or destroy data
12 read-only
14 tools total

Community server · catalogue entry verified 12/06/2026

How to control Crypto_MCP ↓

What Crypto_MCP exposes to your agents

Read (12) Write / Execute (1) Destructive / Financial (0)
High Risk

The most dangerous Crypto_MCP tools

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

How to control Crypto_MCP

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

Cap read operations
{
  "aes_decrypt": {
    "limits": [
      {
        "counter": "aes_decrypt_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 Crypto_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 CRYPTO_MCP →

Free to start. No card required.

All 14 Crypto_MCP tools

Questions about Crypto_MCP

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

The Crypto_MCP server is primarily read-only with 12 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 Crypto_ MCP server expose? +

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

How do I enforce a policy on Crypto_MCP? +

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

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

Free to start. No card required.

14 Crypto_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.