Send coins using shielded transaction
AI agents use zsend-coins to commit financial operations through Cryptocurrency Daemon MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates cryptocurrency transfers using shielded (privacy-preserving) transactions. Moving funds is a Financial action with critical severity because an AI agent misusing this tool could irreversibly send funds to unintended addresses, and the shielded nature makes tracing/recovery even harder.
From the tool's definition "Send coins using shielded transaction" — explicitly moves cryptocurrency funds between addresses
Attacks that exploit this kind of access
Send coins using shielded transaction. It is categorised as a Financial tool in the Cryptocurrency Daemon MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Cryptocurrency Daemon MCP Server MCP server in PolicyLayer and add a rule for zsend-coins: 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 Cryptocurrency Daemon MCP Server. Nothing to install.
zsend-coins 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 zsend-coins 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 zsend-coins. 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.
zsend-coins is provided by the Cryptocurrency Daemon MCP Server MCP server (raw391/coin_daemon_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 →