Transfer native S token or ERC20 tokens to another address. Supports token symbols (S, wS, WETH, USDC) or token contract addresses. If private key is not provided, uses WALLET_PRIVATE_KEY from environment.
AI agents use transfer to commit financial operations through Sonic Blockchain MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money (cryptocurrency tokens) and creates irreversible financial obligations. It is categorized as Financial rather than Destructive or Write because its primary purpose is token/fund transfer rather than deletion. The severity is critical because an AI agent with access to this tool and a valid private key could drain wallet funds or transfer assets without intended authorization.
From the tool's definition Tool description explicitly states 'Transfer native S token or ERC20 tokens to another address' and 'uses WALLET_PRIVATE_KEY from environment'.
Attacks that exploit this kind of access
Transfer native S token or ERC20 tokens to another address. Supports token symbols (S, wS, WETH, USDC) or token contract addresses. If private key is not provided, uses WALLET_PRIVATE_KEY from environment. It is categorised as a Financial tool in the Sonic Blockchain MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Sonic Blockchain MCP Server MCP server in PolicyLayer and add a rule for transfer: 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 Sonic Blockchain MCP Server. Nothing to install.
transfer 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 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. 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 is provided by the Sonic Blockchain MCP Server MCP server (tairon-ai/sonic-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 →