Transfer ERC20 tokens from the connected wallet to another address
AI agents use transferERC20 to commit financial operations through MCP Ethers Wallet — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves financial value (ERC20 tokens) and commits financial obligations. While it is reversible in the sense that a receiving party could return tokens, the transfer itself is an irreversible action that immediately debits the wallet. An AI agent with access to this tool could drain wallet funds without explicit user approval per transaction. This is the most severe risk category applicable.
From the tool's definition transferERC20 transfers tokens from the connected wallet to another address. Tokens represent financial value on blockchain networks. The tool directly moves cryptocurrency assets between addresses, which constitutes a financial transaction.
Documented attack patterns abuse exactly the kind of access transferERC20 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Ethers Wallet, and nothing reaches the server without passing your rules. This is the rule we recommend for transferERC20:
{
"version": "1",
"default": "deny",
"tools": {
"transferERC20": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transferERC20 is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer ERC20 tokens from the connected wallet to another address. It is categorised as a Financial tool in the MCP Ethers Wallet MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for transferERC20: 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 MCP Ethers Wallet. Nothing to install.
transferERC20 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 transferERC20 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 transferERC20. 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.
transferERC20 is provided by the MCP Ethers Wallet MCP server (crazyrabbitltc/mcp-ethers-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Ethers Wallet, 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.
69 MCP Ethers Wallet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.