swap_send

THE RISK

High Risk

Why swap_send needs a policy

Submitting a signed transaction to the blockchain is an irreversible execution of a swap operation. Once broadcast, the transaction cannot be undone. It triggers an external on-chain operation whose effects depend on the transaction arguments.

From the tool's definition Submit signed transactions for a swap order

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

POLICY

How to control swap_send

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "swap_send": {
      "limits": [
        {
          "counter": "swap_send_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

swap_send stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. 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.

RATE-LIMIT 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 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 →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Bitget Wallet MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about swap_send

What does the swap_send tool do? +

Submit signed transactions for a swap order. It is categorised as a Execute tool in the Bitget Wallet MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on swap_send? +

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

swap_send is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit swap_send? +

Yes. Add a rate_limit block to the swap_send 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 swap_send completely? +

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

swap_send 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 →