transfer_stx

Transfer STX tokens to a recipient address. Signs and broadcasts the transaction. Example: To send 2 STX, use amount

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

WHAT IT DOES

What transfer_stx does on Aibtc

AI agents use transfer_stx 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_stx is rated Critical

This tool moves cryptocurrency (STX tokens) from one address to another and broadcasts the transaction to the blockchain. This is an irreversible financial transaction that commits value. It represents the highest risk category (Financial) with critical severity due to the potential for significant monetary loss if an AI agent is compromised or misled into sending tokens to an attacker's address.

From the tool's definition Tool name is 'transfer_stx' and description states 'Transfer STX tokens to a recipient address. Signs and broadcasts the transaction.' STX is a cryptocurrency token, making this a direct financial operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

transfer_stx Approval-gated

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

FAQ

Questions about transfer_stx

What does the transfer_stx tool do? +

Transfer STX tokens to a recipient address. Signs and broadcasts the transaction. Example: To send 2 STX, use amount. 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_stx? +

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

transfer_stx 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_stx? +

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

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

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