kaspa_connect

THE RISK

High Risk

Why kaspa_connect needs a policy

Establishing a network connection triggers an external operation (connecting to a live blockchain network node). It doesn't read, write, or delete data on its own, but it initiates an active network session whose effects depend on the chosen argument (e.g., mainnet vs. testnet). This is an operational side-effect that falls under Execute.

From the tool's definition Connect to Kaspa network (mainnet, testnet-10, devnet, simnet)

Documented attack patterns abuse exactly the kind of access kaspa_connect gives an agent:

POLICY

How to control kaspa_connect

PolicyLayer is an MCP gateway — it sits between your AI agents and Kaspa MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for kaspa_connect:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kaspa_connect": {
      "limits": [
        {
          "counter": "kaspa_connect_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

kaspa_connect stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Kaspa MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kaspa MCP Server tools

Financial kaspa_send_from_wallet Send Kaspa from your wallet (simplified version) Financial kaspa_send_transaction Send a Kaspa transaction Write kaspa_create_wallet Create or import a Kaspa wallet Write kaspa_generate_mnemonic Generate a new mnemonic phrase for wallet creation Write kaspa_setup_preconfigured_wallet Setup wallet using preconfigured credentials from environment variables (KASPA_WALLET_MNEM Write kaspa_unsubscribe_balance Unsubscribe from balance change notifications Read kaspa_get_balance Get balance for a Kaspa address Read kaspa_get_fee_recommendations Get fee recommendations for different priority levels

All 15 Kaspa MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Kaspa MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kaspa_connect

What does the kaspa_connect tool do? +

Connect to Kaspa network (mainnet, testnet-10, devnet, simnet). It is categorised as a Execute tool in the Kaspa MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kaspa_connect? +

Register the Kaspa MCP Server MCP server in PolicyLayer and add a rule for kaspa_connect: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Kaspa MCP Server. Nothing to install.

What risk level is kaspa_connect? +

kaspa_connect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kaspa_connect? +

Yes. Add a rate_limit block to the kaspa_connect rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block kaspa_connect completely? +

Set action: deny in the PolicyLayer policy for kaspa_connect. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides kaspa_connect? +

kaspa_connect is provided by the Kaspa MCP Server MCP server (pichukov/kaspa-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kaspa MCP Server tool call.

Start from Kaspa MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →