A hardware security module representing server-enforced controls for AI trading agents

Coinbase Adds Hard Trading Limits for AI Agents—But Open Orders Need a Second Look

• November 13, 2026 11:12 pm • Comments

Coinbase is putting hard limits between an AI trading agent and a customer’s money.

The exchange’s new Agent Controls let users cap the size of a single trade, limit total trading volume over 24 hours and automatically stop new trades when a portfolio crosses a chosen loss threshold. The important detail is where those rules live: Coinbase says they run on its own servers, outside the agent’s control.

According to Coinbase, an agent cannot raise or remove those limits on its own. Customers manage them through Coinbase’s app or website, behind the account’s password and two-factor authentication.

The maximum-trade setting is denominated in dollars, while the volume limit measures cumulative trading over 24 hours. Coinbase says an order that would exceed that daily ceiling will not go through.

The auto-stop uses a portfolio-loss percentage and blocks new trades until the customer turns trading back on. Product-level permissions for crypto, equities and derivatives are listed as coming soon.

Coinbase introduced the controls on November 11 as part of Coinbase for Agents, its MCP-based product for research and trading. The company’s own disclaimer says agents can make mistakes and customers remain responsible for their activity.

That is a meaningful shift for agentic trading. Telling a bot to “be careful” is not a risk system.

A server-enforced ceiling is.

The three controls solve different problems. A maximum trade size limits one bad order, while a 24-hour volume cap limits the damage from many small orders.

Auto-stop halts new trading after a portfolio-level loss threshold is reached.

But “stop” needs to be read carefully. CryptoSlate notes that open orders can remain active after agent access is revoked, because the new controls stop an agent from placing additional trades but do not automatically erase limit instructions already accepted by the exchange, leaving customers responsible for reviewing and cancelling any resting order they no longer want in the market.

In other words, cutting off the agent does not necessarily cancel instructions already sitting on the exchange’s books.

That distinction matters in a fast market. A resting limit order can still execute after the bot that placed it has been disconnected.

Users need to review open orders separately instead of treating access revocation as a complete kill switch.

The report also distinguishes pausing new agent activity from managing existing exchange orders. That means the safest shutdown procedure includes an order-book review and explicit cancellation of anything the customer no longer wants executed.

That is operationally different from simply disconnecting an app. It is a small detail with potentially large consequences during a sharp price move.

The same reporting says users can revoke an agent’s access at any time and that Coinbase’s controls are enforced outside the AI model. Existing orders are the exception customers must handle deliberately, because they were already accepted by the exchange before access ended.

The practical sequence is therefore clear: stop new agent activity, inspect every resting order, cancel unwanted instructions and only then treat the session as closed. Skipping the middle steps can leave market exposure behind.

Coinbase is effectively separating an agent’s trading intelligence from the account’s ultimate risk policy. That is the right architecture.

The agent can search, analyze and submit orders, while the exchange enforces boundaries the agent cannot negotiate away.

It still leaves the customer responsible for choosing sensible limits. A $100 maximum order does little if a bot can place hundreds of them, while a daily volume cap does not by itself prevent concentration in one volatile asset.

The controls work best as a stack, not as isolated switches.

AI agents are moving from answering questions to taking financial actions. Coinbase’s update acknowledges that the safety layer has to become just as programmable—and considerably less trusting—as the agent itself.

Join the conversation!

We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.