transfer_submit

THE RISK

Critical Risk

Why transfer_submit needs a policy

The Financial category is most severe and applies when tools move money or commit financial obligations. A 'transfer_submit' function on a wallet API is explicitly designed to execute cryptocurrency transfers—direct financial transactions. An AI agent misusing this without proper authorization could transfer user funds without consent, creating maximum blast radius.

From the tool's definition Tool name 'transfer_submit' indicates submission of financial transfers. Combined with server context exposing a wallet API and sibling tools like 'balance' and 'check_swap_token', this tool almost certainly facilitates movement of cryptocurrency funds.

Documented attack patterns abuse exactly the kind of access transfer_submit gives an agent:

POLICY

How to control transfer_submit

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_submit:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_submit": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to transfer_submit is blocked until a human approves it. The rest of the server keeps working.

Create a free account and register Bitget Wallet MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bitget Wallet MCP Server tools

Financial transfer_make_order transfer_make_order Execute swap_confirm swap_confirm Execute swap_make_order swap_make_order Execute swap_quote swap_quote Execute swap_send Submit signed transactions for a swap order. Read security_audit Run a security audit on a token contract (honeypot detection, permission checks, blacklist Read balance balance Read batch_token_info Get info for multiple tokens in one call.

All 39 Bitget Wallet MCP Server tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in Bitget Wallet MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about transfer_submit

What does the transfer_submit tool do? +

transfer_submit. 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.

How do I enforce a policy on transfer_submit? +

Register the Bitget Wallet MCP Server MCP server in PolicyLayer and add a rule for transfer_submit: 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.

What risk level is transfer_submit? +

transfer_submit is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer_submit? +

Yes. Add a rate_limit block to the transfer_submit 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.

How do I block transfer_submit completely? +

Set action: deny in the PolicyLayer policy for transfer_submit. 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.

What MCP server provides transfer_submit? +

transfer_submit 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.

Enforce policy on every Bitget Wallet MCP Server tool call.

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.

CHECK YOUR STACK →