Transfer tokens between wallets
AI agents use TRANSFER to commit financial operations through Solana MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
TRANSFER moves cryptocurrency tokens between wallets, which directly commits financial obligations and moves value. This is the most severe risk category. An AI agent with access to this tool could drain wallets, send funds to attacker-controlled addresses, or execute unauthorized financial transfers.
From the tool's definition Tool name 'TRANSFER' with description 'Transfer tokens between wallets' on a Solana blockchain MCP server. The sibling tool context includes TRADE, DEPLOY_TOKEN, and MINT_NFT, confirming this is a financial transaction system.
Attacks that exploit this kind of access
Transfer tokens between wallets. It is categorised as a Financial tool in the Solana MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Solana MCP Server 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 Solana MCP Server. 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 Solana MCP Server MCP server (pingaifun/ping-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 →