Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet.
AI agents use transfer_native 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 moves cryptocurrency (native tokens like ETH, MATIC, BNB) from one address to another. This directly commits financial obligations and transfers monetary value, making it Financial category. Severity is critical because a misused transfer could drain significant funds with no recovery mechanism, affecting large sums depending on the wallet balance.
From the tool's definition Tool description states it 'Transfer native tokens (ETH, MATIC, etc.) to an address' using 'the configured wallet.' Native tokens represent monetary value and can be transferred directly.
Documented attack patterns abuse exactly the kind of access transfer_native 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:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_native": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_native is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet. 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: 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 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 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. 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 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.