AI agents use btse_transfer to commit financial operations through Btse — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money between accounts/wallets, which constitutes a financial transaction that commits resources and creates financial obligations. Even if transfers are reversible in principle, they represent immediate movement of funds and carry critical risk if an AI agent misuses the tool to transfer funds to unauthorized wallets or accounts. The blast radius is maximal—direct loss of user funds.
From the tool's definition Tool name 'btse_transfer' explicitly transfers funds between wallets. Description states 'Transfer funds between BTSE wallets (e.g. spot to futures, or between isolated margin wallets).' Context shows this is part of a futures trading API server.
Attacks that exploit this kind of access
Transfer funds between BTSE wallets (e.g. spot to futures, or between isolated margin wallets). It is categorised as a Financial tool in the Btse MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Btse MCP server in PolicyLayer and add a rule for btse_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 Btse. Nothing to install.
btse_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 btse_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 btse_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.
btse_transfer is provided by the Btse MCP server (xbotlive/btse-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 →