Transfer tokens from one account to another. Both accounts must be associated with the token first. The sender must sign the transaction - provide senderPrivateKey or ensure sender is in address book with private key.
AI agents use token_transfer to commit financial operations through HashPilot — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves cryptocurrency/tokens between accounts, which is a financial operation with permanent monetary consequences. The tool requires cryptographic signing and can result in loss of funds if misused by an AI agent (wrong recipient, wrong amount, or account compromise via private key exposure). This is the highest severity category as it involves direct financial transfers.
From the tool's definition 'Transfer tokens from one account to another' combined with 'sender must sign the transaction' and requirement for private key handling indicate irreversible movement of financial assets on Hedera blockchain.
Attacks that exploit this kind of access
Transfer tokens from one account to another. Both accounts must be associated with the token first. The sender must sign the transaction - provide senderPrivateKey or ensure sender is in address book with private key. It is categorised as a Financial tool in the HashPilot MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the HashPilot MCP server in PolicyLayer and add a rule for token_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 HashPilot. Nothing to install.
token_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 token_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 token_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.
token_transfer is provided by the HashPilot MCP server (justmert/hashpilot). 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 →