AI agents use send_kaspa to commit financial operations through Kaspa MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves KAS cryptocurrency tokens to another address, which is an irreversible financial transaction. Misuse by an AI agent could result in loss of funds with no ability to recover them, making this critical severity.
From the tool's definition Send KAS tokens to a recipient address
Attacks that exploit this kind of access
Send KAS tokens to a recipient address. It is categorised as a Financial tool in the Kaspa MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Kaspa MCP server in PolicyLayer and add a rule for send_kaspa: 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. Nothing to install.
send_kaspa 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 send_kaspa 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 send_kaspa. 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.
send_kaspa is provided by the Kaspa MCP server (kasanova-io/kaspa-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →