kaspa_setup_preconfigured_wallet

THE RISK

Medium Risk

Why kaspa_setup_preconfigured_wallet needs a policy

This tool creates or configures a new wallet entity by loading private credentials (mnemonic or private key) from environment variables. While wallet setup itself is reversible (unlike financial transfers or destructive operations), it enables access to blockchain assets and is a prerequisite for financial transactions.

From the tool's definition Setup wallet using preconfigured credentials from environment variables (KASPA_WALLET_MNEMONIC or KASPA_WALLET_PRIVATE_KEY) - this creates or initializes a wallet with sensitive key material

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

POLICY

How to control kaspa_setup_preconfigured_wallet

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_setup_preconfigured_wallet:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kaspa_setup_preconfigured_wallet": {
      "limits": [
        {
          "counter": "kaspa_setup_preconfigured_wallet_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

kaspa_setup_preconfigured_wallet stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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.

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 Execute kaspa_connect Connect to Kaspa network (mainnet, testnet-10, devnet, simnet) Write kaspa_create_wallet Create or import a Kaspa wallet Write kaspa_generate_mnemonic Generate a new mnemonic phrase for wallet creation 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kaspa_setup_preconfigured_wallet

What does the kaspa_setup_preconfigured_wallet tool do? +

Setup wallet using preconfigured credentials from environment variables (KASPA_WALLET_MNEMONIC or KASPA_WALLET_PRIVATE_KEY). It is categorised as a Write tool in the Kaspa MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kaspa_setup_preconfigured_wallet? +

Register the Kaspa MCP Server MCP server in PolicyLayer and add a rule for kaspa_setup_preconfigured_wallet: 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_setup_preconfigured_wallet? +

kaspa_setup_preconfigured_wallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kaspa_setup_preconfigured_wallet? +

Yes. Add a rate_limit block to the kaspa_setup_preconfigured_wallet 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_setup_preconfigured_wallet completely? +

Set action: deny in the PolicyLayer policy for kaspa_setup_preconfigured_wallet. 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_setup_preconfigured_wallet? +

kaspa_setup_preconfigured_wallet 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 →