AI agents use kaspa_create_wallet to create or update resources in Kaspa MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kaspa MCP Server environment.
Creating a wallet involves generating or importing private keys and storing wallet state—a reversible but security-sensitive write operation. The tool modifies persistent wallet state. While not destructive (wallet can be recreated), this is more severe than a simple read due to the cryptographic nature and financial implications of wallet creation on a blockchain network.
From the tool's definition Tool name 'kaspa_create_wallet' and description 'Create or import a Kaspa wallet' indicate creation of wallet objects and cryptographic key material.
Documented attack patterns abuse exactly the kind of access kaspa_create_wallet gives an agent:
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_create_wallet:
{
"version": "1",
"default": "deny",
"tools": {
"kaspa_create_wallet": {
"limits": [
{
"counter": "kaspa_create_wallet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} kaspa_create_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.
Free to start. No card required.
Create or import a Kaspa wallet. 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.
Register the Kaspa MCP Server MCP server in PolicyLayer and add a rule for kaspa_create_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.
kaspa_create_wallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the kaspa_create_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.
Set action: deny in the PolicyLayer policy for kaspa_create_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.
kaspa_create_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.
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.
Free to start. No card required.
15 Kaspa MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.