Transfer ERC20 tokens to an address. Uses the configured wallet.
AI agents use transfer_erc20 to commit financial operations through EVM MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves financial assets (ERC20 tokens, which are cryptocurrencies or tokenized value) from one address to another. An AI agent with unconstrained access could drain wallets, send funds to attacker addresses, or commit unintended financial transactions.
From the tool's definition Tool description states 'Transfer ERC20 tokens to an address' — this moves cryptocurrency assets from the configured wallet to another address. ERC20 tokens represent financial value on Ethereum-compatible networks.
Documented attack patterns abuse exactly the kind of access transfer_erc20 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_erc20:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_erc20": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_erc20 is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer ERC20 tokens to an address. Uses the configured wallet. It is categorised as a Financial tool in the EVM MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for transfer_erc20: 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 EVM MCP Server. Nothing to install.
transfer_erc20 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_erc20 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_erc20. 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_erc20 is provided by the EVM MCP Server MCP server (mcpdotdirect/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from EVM 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.
25 EVM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.