Transfer fungible tokens to another address
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.
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
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.
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.
transfer_ft is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →