transfer_ft

Transfer fungible tokens to another address

SERVERStacks AI MCP Server SOURCEstack-ai-mcp/stacks-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/transfer-ft.md

WHAT IT DOES

What transfer_ft does on Stacks AI MCP Server

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

RISK

Why transfer_ft is rated Critical

This tool directly moves financial assets (fungible tokens) from one address to another. Token transfers constitute irreversible financial transactions that commit the user's assets to another party. Even though the tool itself is not named with overtly destructive language, it represents a direct financial obligation/movement.

From the tool's definition Tool name 'transfer_ft' and description 'Transfer fungible tokens to another address' explicitly indicate movement of cryptocurrency/tokens (fungible tokens on Stacks Bitcoin Layer 2) to another wallet address.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_ft safely

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

transfer_ft Approval-gated

Any call to transfer_ft 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_ft": {
      "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 Stacks AI MCP Server, apply this rule, and every transfer_ft call is checked against it from then on.

FAQ

Questions about transfer_ft

What does the transfer_ft tool do? +

Transfer fungible tokens to another address. It is categorised as a Financial tool in the Stacks AI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_ft? +

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

What risk level is transfer_ft? +

transfer_ft 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_ft? +

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

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

transfer_ft is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-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 Stacks AI MCP Server, and thousands of servers like it.

This server

All 200 Stacks AI MCP Server tools → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge →transfer_sites on A3plus → All critical-risk MCP tools → The MCP Attack Database →

Guides

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