Create a new transfer between accounts, addresses, or financial institutions
AI agents use brale_create_transfer to commit financial operations through Brale API MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool commits financial obligations by transferring stablecoins or other assets between parties. Misuse by an AI agent could result in unauthorized fund transfers, loss of assets, or fraudulent transactions. Financial operations represent the highest severity risk category.
From the tool's definition Tool name 'brale_create_transfer' and description 'Create a new transfer between accounts, addresses, or financial institutions' directly indicate movement of money/assets.
Attacks that exploit this kind of access
Create a new transfer between accounts, addresses, or financial institutions. It is categorised as a Financial tool in the Brale API MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Brale API MCP Server MCP server in PolicyLayer and add a rule for brale_create_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 Brale API MCP Server. Nothing to install.
brale_create_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 brale_create_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 brale_create_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.
brale_create_transfer is provided by the Brale API MCP Server MCP server (stablecoinxyz/brale-api-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 →