transfer_token

Transfer any SIP-010 token to a recipient address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/transfer-token.md

WHAT IT DOES

What transfer_token does on Aibtc

AI agents use transfer_token to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why transfer_token is rated Critical

This tool moves cryptocurrency tokens to arbitrary recipient addresses, which constitutes a direct financial transaction. An AI agent with access to this tool could transfer funds without authorization, resulting in irreversible loss of assets. This is the most severe category (Financial > Destructive > Execute > Write > Read) due to the direct financial impact and potential for unauthorized value transfer.

From the tool's definition Tool description explicitly states 'Transfer any SIP-010 token to a recipient address' with support for recognized tokens (sBTC, USDCx, ALEX, DIKO).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_token safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_token, this is the rule to start with:

transfer_token Approval-gated

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

View as policy code

policy.json

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

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every transfer_token call is checked against it from then on.

FAQ

Questions about transfer_token

What does the transfer_token tool do? +

Transfer any SIP-010 token to a recipient address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_token? +

Register the Aibtc MCP server in PolicyLayer and add a rule for transfer_token: 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 Aibtc. Nothing to install.

What risk level is transfer_token? +

transfer_token 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_token? +

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

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

transfer_token is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →