Kaspa MCP

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

1 destructive tool with no built-in limits. Policy required.

Last updated:

2 can modify or destroy data
5 read-only
7 tools total

Community server · catalogue entry verified 29/06/2026

How to control Kaspa MCP ↓

What Kaspa MCP exposes to your agents

Read (5) Write / Execute (1) Destructive / Financial (1)
Critical Risk

The most dangerous Kaspa MCP tools

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

How to control Kaspa MCP

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

Block financial tools by default
{
  "send_kaspa": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations
{
  "generate_mnemonic": {
    "limits": [
      {
        "counter": "generate_mnemonic_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_balance": {
    "limits": [
      {
        "counter": "get_balance_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 Kaspa 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 KASPA →

Instant setup, no code required.

All 7 Kaspa MCP tools

Questions about Kaspa MCP

Can an AI agent move money through the Kaspa MCP server? +

Yes. The Kaspa MCP server exposes 1 financial tools including send_kaspa. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Kaspa MCP? +

The Kaspa MCP server has 1 write tools including generate_mnemonic. 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 Kaspa MCP.

How many tools does the Kaspa MCP server expose? +

7 tools across 2 categories: Read, Write. 5 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Kaspa MCP? +

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

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

Instant setup, no code required.

7 Kaspa 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.