transfer_get_order

THE RISK

Low Risk

Why transfer_get_order needs a policy

This tool queries and retrieves the status of an existing transfer order. It performs polling to obtain status information but does not create, modify, delete, or execute any transactions or external operations. The 'get' verb and query semantics align with Read category.

From the tool's definition Tool name 'transfer_get_order' and description 'Query transfer order status. Poll until terminal status' indicate a read-only operation that retrieves order information without modifying data.

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

POLICY

How to control transfer_get_order

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_get_order": {}
  }
}

transfer_get_order is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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.

CAP 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 Financial transfer_submit transfer_submit 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

All 39 Bitget Wallet MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about transfer_get_order

What does the transfer_get_order tool do? +

Query transfer order status. Poll until terminal status (SUCCESS or FAILED). It is categorised as a Read tool in the Bitget Wallet MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on transfer_get_order? +

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

What risk level is transfer_get_order? +

transfer_get_order is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit transfer_get_order? +

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

How do I block transfer_get_order completely? +

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

What MCP server provides transfer_get_order? +

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

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 →