Transfer native tokens (BNB, ETH, MATIC, etc.) to an address
AI agents use transfer_native_token to commit financial operations through Sperax Ecosystem Crypto & DeFI MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool enables transfer of native blockchain tokens (BNB, ETH, MATIC), which are financial assets with real monetary value. Any misuse by an AI agent could result in irreversible loss of funds. While Destructive actions typically affect data, financial transfers are more severe due to direct monetary loss and are therefore classified as Financial.
From the tool's definition Transfer native tokens (BNB, ETH, MATIC, etc.) to an address — this directly moves cryptocurrency/native blockchain assets from one address to another, constituting a financial transaction that commits monetary value.
Documented attack patterns abuse exactly the kind of access transfer_native_token gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_native_token:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_native_token": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_native_token is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer native tokens (BNB, ETH, MATIC, etc.) to an address. It is categorised as a Financial tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for transfer_native_token: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
transfer_native_token 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 transfer_native_token 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 transfer_native_token. 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.
transfer_native_token is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI 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.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.