Critical Risk

transfer_stx

Transfer STX tokens to a recipient address. Signs and broadcasts the transaction. Example: To send 2 STX, use amount "2000000" (micro-STX). 1 STX = 1,000,000 micro-STX

Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@aibtc/mcp-server Financial Risk 5/5

AI agents use transfer_stx to initiate financial transactions through Aibtc. Financial operations involve real money and are irreversible once processed. Intercept blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

transfer_stx moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

io-github-aibtcdev-mcp-server.yaml
tools:
  transfer_stx:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full Aibtc policy for all 288 tools.

Tool Name transfer_stx
Category Financial
MCP Server Aibtc MCP Server
Risk Level Critical

View all 288 tools →

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 "2000000" (micro-STX). 1 STX = 1,000,000 micro-STX. 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? +

Add a rule in your Intercept YAML policy under the tools section for transfer_stx. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.

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 Intercept 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 Intercept 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 (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Aibtc

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.