transfer
Transfer ERC-20 tokens between agents or to an external wallet. A 1% platform fee applies. Requires api_key.
This record as markdown: /tools/io-github-wirternow-agent-bank/transfer.md
What transfer does on Ai Agent Bank
AI agents use transfer to commit financial operations through Ai Agent Bank, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
token | string | — | Token symbol: USDC, WMATIC, WETH (defaults to USDC) |
amount | number | Yes | Amount of tokens to transfer |
api_key | string | Yes | Your api_key from register_agent |
to_agent_id | string | — | UUID of the receiving agent (optional if recipient_address provided) |
from_agent_id | string | Yes | UUID of the sending agent |
recipient_address | string | — | Wallet address of recipient (optional if to_agent_id provided) |
Parameters from the server's own tool schema.
Why transfer is rated Critical
This tool directly moves money (ERC-20 tokens, specifically USDC on Polygon per server context) between parties. Misuse by an AI agent could result in unauthorized token transfers, loss of funds, or commitment of financial resources. This is the highest severity risk category. The requirement for an API key does not mitigate the core financial risk once authenticated.
From the tool's definition Tool is described as 'Transfer ERC-20 tokens between agents or to an external wallet' with a platform fee, indicating it moves cryptocurrency (USDC per server description) and commits financial obligations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs transfer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer, this is the rule to start with:
Any call to transfer is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ai Agent Bank, apply this rule, and every transfer call is checked against it from then on.
Questions about transfer
Transfer ERC-20 tokens between agents or to an external wallet. A 1% platform fee applies. Requires api_key. It is categorised as a Financial tool in the Ai Agent Bank MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
transfer accepts 6 parameters: token, amount, api_key, to_agent_id, from_agent_id, recipient_address. Required: amount, api_key, from_agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank 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 Ai Agent Bank. 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 Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
Across the catalogue