Transfer HBAR between Hedera accounts. EXECUTES: CryptoTransfer transaction from source to destination REQUIRES: Operator account must be source OR have signing authority COSTS: Standard network transaction fee USE FOR: Funding accounts, payments, moving HBAR between wallets.
AI agents use transfer_hbar to commit financial operations through HashPilot — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool transfers cryptocurrency (HBAR) between accounts, which constitutes a financial transaction that moves monetary value. Even though it requires operator authorization, an AI agent with access to signing credentials could irreversibly move funds.
From the tool's definition Tool description states 'Transfer HBAR between Hedera accounts' and 'CryptoTransfer transaction from source to destination' with explicit mention of 'payments, moving HBAR between wallets.' HBAR is the native cryptocurrency of Hedera blockchain, making this a…
Attacks that exploit this kind of access
Transfer HBAR between Hedera accounts. EXECUTES: CryptoTransfer transaction from source to destination REQUIRES: Operator account must be source OR have signing authority COSTS: Standard network transaction fee USE FOR: Funding accounts, payments, moving HBAR between wallets. 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 transfer_hbar: 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.
transfer_hbar 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_hbar 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_hbar. 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_hbar 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 →