Transfer value from the caller’s wallet to another address. FUNCTIONALITY • Native ETH transfer (simple payment) • ERC-20 transfer (requires tokenAddress or known tokenSymbol) • ENS resolution for recipient VALIDATION & LOGGING • Ensures wallet signer configured, token decimals fetched automatica...
AI agents use ab_transfer_token to commit financial operations through Society Abstract MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool commits financial obligations by transferring funds (native ETH or ERC-20 tokens) from the caller's wallet to recipient addresses. Even though it operates on testnets and mainnets, the capability to move real value makes it a Financial category tool.
From the tool's definition Tool performs 'Transfer value from the caller's wallet to another address' with support for 'Native ETH transfer' and 'ERC-20 transfer'. Common use-cases explicitly include 'Payout scripted rewards' and 'Move workshop faucet tokens to students'.
Attacks that exploit this kind of access
Transfer value from the caller’s wallet to another address. FUNCTIONALITY • Native ETH transfer (simple payment) • ERC-20 transfer (requires tokenAddress or known tokenSymbol) • ENS resolution for recipient VALIDATION & LOGGING • Ensures wallet signer configured, token decimals fetched automatically • Logs tx hash on success so the agent can create explorer links COMMON USE-CASES • Payout scripted rewards • Move workshop faucet tokens to students • Automation flows needing programmatic payment. It is categorised as a Financial tool in the Society Abstract MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Society Abstract MCP server in PolicyLayer and add a rule for ab_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 Society Abstract MCP. Nothing to install.
ab_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 ab_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 ab_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.
ab_transfer_token is provided by the Society Abstract MCP server (wearesociety/abstract_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →