AI agents use kaspa_send_transaction to commit financial operations through Kaspa MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves Kaspa cryptocurrency by broadcasting a transaction to the network. Cryptocurrency transfers are irreversible once confirmed on-chain, making this both Financial and potentially Destructive. Financial is the most severe applicable category. Misuse by an AI agent could result in irreversible loss of funds, warranting critical severity.
From the tool's definition "Send a Kaspa transaction" — directly transmits cryptocurrency on the Kaspa network
Documented attack patterns abuse exactly the kind of access kaspa_send_transaction 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_send_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"kaspa_send_transaction": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to kaspa_send_transaction is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Send a Kaspa transaction. It is categorised as a Financial tool in the Kaspa MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Kaspa MCP Server MCP server in PolicyLayer and add a rule for kaspa_send_transaction: 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_send_transaction is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the kaspa_send_transaction 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_send_transaction. 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_send_transaction 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.