Send a specified amount of nano units from a predefined Nano account to a destination Nano account.
AI agents use nano_send to commit financial operations through Nano Currency MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly transfers Nano cryptocurrency from one account to another. This is an irreversible financial transaction — once Nano is sent on the network, it cannot be recalled. Misuse by an AI agent could result in unauthorized or erroneous transfer of funds, making this critical severity under the Financial category.
From the tool's definition "Send a specified amount of nano units from a predefined Nano account to a destination Nano account"
Documented attack patterns abuse exactly the kind of access nano_send gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nano Currency MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for nano_send:
{
"version": "1",
"default": "deny",
"tools": {
"nano_send": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to nano_send is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Send a specified amount of nano units from a predefined Nano account to a destination Nano account. It is categorised as a Financial tool in the Nano Currency MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Nano Currency MCP Server MCP server in PolicyLayer and add a rule for nano_send: 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 Nano Currency MCP Server. Nothing to install.
nano_send 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 nano_send 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 nano_send. 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.
nano_send is provided by the Nano Currency MCP Server MCP server (kilkelly/nano-currency-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nano Currency 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.
6 Nano Currency MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.