transfer_between_accounts
AI agents use transfer_between_accounts to commit financial operations through Finance App — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money between accounts, which commits financial obligations and transfers value. Even without an explicit description, the name combined with the server's purpose (personal finance accounting) and sibling tools (account management, transactions, budgets) makes the financial impact unambiguous.
From the tool's definition Tool name 'transfer_between_accounts' on a 'Double-entry accounting service for personal finance' server with sibling tools like 'create_account', 'get_account_balance', and 'delete_transaction'.
Attacks that exploit this kind of access
transfer_between_accounts. It is categorised as a Financial tool in the Finance App MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Finance App MCP server in PolicyLayer and add a rule for transfer_between_accounts: 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 Finance App. Nothing to install.
transfer_between_accounts 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_between_accounts 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_between_accounts. 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_between_accounts is provided by the Finance App MCP server (youssefaltai/finance-app). 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 →