transfer_erc20
Transfer ERC20 tokens to another address
This record as markdown: /tools/testinguser1111111-sei-mcp-server/transfer-erc20.md
What transfer_erc20 does on SEI MCP Server V2
AI agents use transfer_erc20 to commit financial operations through SEI MCP Server V2, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why transfer_erc20 is rated Critical
This tool moves cryptocurrency tokens (ERC20) from one address to another on the Sei blockchain. Token transfers are irreversible financial transactions — once sent, tokens cannot be recovered without the recipient's cooperation. This constitutes a direct financial operation with high blast radius if misused by an AI agent (e.g., sending tokens to wrong address or draining a wallet).
From the tool's definition Transfer ERC20 tokens to another address
Attacks that exploit this kind of access
The rule that runs transfer_erc20 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_erc20, this is the rule to start with:
Any call to transfer_erc20 is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every transfer_erc20 call is checked against it from then on.
Questions about transfer_erc20
Transfer ERC20 tokens to another address. It is categorised as a Financial tool in the SEI MCP Server V2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the SEI MCP Server V2 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 SEI MCP Server V2. 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 SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SEI MCP Server V2, and thousands of servers like it.
Across the catalogue