Tether’s Wallet Development Kit places spending limits on AI agents in developers’ hands

Tether CEO Paolo Ardoino envisions AI agents that can hold and spend USDT, but the technical design of the Wallet Development Kit (WDK) puts the responsibility for spending limits on developers.

How the WDK unlock works

The WDK command‑line wallet (CLI) runs a daemon that holds an unlocked wallet for a default five‑minute session. On macOS and Linux the daemon’s socket is accessible to any process running under the same operating‑system user, allowing that process to request signatures without re‑entering the passphrase.

What the CLI does not enforce

While the session timer controls how long the wallet stays unlocked, it does not set a maximum amount, recipient list, or require fresh approval for each payment. The CLI’s recommended workflow—previewing a transaction, confirming details, then executing—relies on the calling application to enforce those checks.

Developer‑level controls

Developers can use the WDK SDK to define ALLOW and DENY rules for recipients and amounts, but these are optional, local checks that do not run on‑chain. They also do not track cumulative spending, so a product must maintain its own accounting if it promises a daily budget or similar limit.

Model Context Protocol (MCP) toolkit

The bundled MCP server provides structured calls for AI clients. It can be configured to require explicit user approval before broadcasting, but the same underlying unlocked wallet can still be accessed via other paths if the developer does not restrict them.

Practical implications

For users, the key question is what an AI assistant is authorized to spend and where it can send funds. A wallet password or a single approval prompt is insufficient unless the surrounding software enforces the intended limits.