AI agents use transfer_make_order to commit financial operations through Bitget Wallet MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool almost certainly moves funds or commits financial obligations by creating transfer/order instructions on blockchain networks. Even if it generates unsigned transactions (as the server description mentions for swaps), creating orders that move money is a Financial risk. An AI agent could misuse this to transfer user assets, execute unauthorized trades, or commit financial obligations.
From the tool's definition Tool named 'transfer_make_order' on a wallet/exchange API server (Bitget Wallet). The name strongly indicates money movement ('transfer') and order creation ('make_order').
Documented attack patterns abuse exactly the kind of access transfer_make_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitget Wallet MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_make_order:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_make_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_make_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
transfer_make_order. It is categorised as a Financial tool in the Bitget Wallet MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bitget Wallet MCP Server MCP server in PolicyLayer and add a rule for transfer_make_order: 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 Bitget Wallet MCP Server. Nothing to install.
transfer_make_order 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_make_order 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_make_order. 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_make_order is provided by the Bitget Wallet MCP Server MCP server (bitget-wallet-ai-lab/bitget-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitget Wallet MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Bitget Wallet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.