Constraints: amount, frequency, geography, time windows
Last updated: · Leutrim Miftaraj
Constraints turn a blanket permission into precise authority: amounts limited per action and per period (reserved atomically against race conditions), frequency limits per day or month, geographic allow-lists by ISO 3166 and UTC time windows.
Atomic reservation
Two parallel purchases may never exceed a monthly limit together: verify reserves the amount atomically (15-minute TTL); only the consumption booking makes it final. The third parallel attempt receives MD-303 — deterministically.
Frequency and context
frequency_limit counts consumptions within the window (MD-305 when exceeded); geo[] checks the country of execution, time_window the time of day including the midnight wrap (both MD-306). An agent shopping overseas at night is stopped — before damage occurs.
Every deny has exactly one code
The first failed check in the deterministic order supplies the primary code — 19 stable codes, machine-evaluable, the basis for later loss statistics.
Key takeaway
Limits are the product: the more precise the constraint language, the more authority people dare to delegate.
Try it yourself
Issue your first agent mandate and check your first decision with its receipt — free, in a few minutes.