High Risk →

swap_confirm

swap_confirm

How to control swap_confirm ↓

What swap_confirm does on Bitget Wallet MCP Server

AI agents invoke swap_confirm to trigger actions in Bitget Wallet MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why swap_confirm needs a policy

The tool name 'swap_confirm' strongly implies confirming or finalizing a token swap transaction across blockchains. Based on the server description, this server generates swap transaction data. Confirming a swap is an Execute-level action (triggering an external blockchain operation), and could be Financial if it moves tokens of value. The description is empty, reducing confidence.

From the tool's definition Tool name 'swap_confirm' on a server that 'generate[s] unsigned swap transaction data across various blockchains'

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

How to control swap_confirm

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "swap_confirm": {
      "limits": [
        {
          "counter": "swap_confirm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Bitget Wallet MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about swap_confirm

What does the swap_confirm tool do? +

swap_confirm. 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_confirm? +

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

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

Can I rate-limit swap_confirm? +

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

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

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

Free to start. No card required.

39 Bitget Wallet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.