transfer_btc

Transfer BTC to a recipient address.

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-btc.md

WHAT IT DOES

What transfer_btc does on Aibtc

AI agents use transfer_btc 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_btc is rated Critical

This tool moves money (Bitcoin) irreversibly to a specified recipient, creating financial obligations and potential loss of funds if misused by an agent. This is a Financial category tool with critical severity due to the high blast radius—any unauthorized or misdirected transfer cannot be easily reversed.

From the tool's definition Tool name 'transfer_btc' and description 'Transfer BTC to a recipient address' explicitly indicate movement of cryptocurrency funds to an external address.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_btc 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_btc, this is the rule to start with:

transfer_btc Approval-gated

Any call to transfer_btc 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_btc": {
      "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_btc call is checked against it from then on.

FAQ

Questions about transfer_btc

What does the transfer_btc tool do? +

Transfer BTC to a recipient address. 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_btc? +

Register the Aibtc MCP server in PolicyLayer and add a rule for transfer_btc: 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_btc? +

transfer_btc 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_btc? +

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

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

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