transfer_token
Transfer ERC20 tokens to an address
This record as markdown: /tools/chulanpro5-evm-mcp-server/transfer-token.md
What transfer_token does on EVM MCP Server
AI agents use transfer_token to commit financial operations through EVM MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why transfer_token is rated Critical
Token transfers on blockchain networks directly move monetary value. An AI agent with misuse of this tool could transfer user funds to unauthorized addresses, resulting in irreversible loss of financial assets. This is classified as Financial rather than Destructive because it primarily moves assets rather than destroying them, though the impact is severe.
From the tool's definition Tool description states 'Transfer ERC20 tokens to an address' - this moves cryptocurrency/tokens between addresses, which constitutes a financial transaction.
Attacks that exploit this kind of access
The rule that runs transfer_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EVM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_token, this is the rule to start with:
Any call to transfer_token is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every transfer_token call is checked against it from then on.
Questions about transfer_token
Transfer ERC20 tokens to an address. 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_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 EVM MCP Server. Nothing to install.
transfer_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_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_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_token is provided by the EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EVM MCP Server, and thousands of servers like it.
Across the catalogue