An agent that types 5000 instead of 500 into a daily budget spends ten times the plan until someone notices. Between the agency and the client, that money is a dispute about who authorised the change. MolTrust gives you a written limit per ad account and a record per change that settles the question from the documents, not from memory.
| Control | What it does |
|---|---|
| Daily cap per campaign | Any budget above it is forbidden before it reaches Amazon. |
| Account-wide daily cap | The sum across all campaigns after the change stays under the line you set. |
| Approval threshold | Above it, the change waits for a signature from a person named in the mandate. |
| Bid limits | Largest bid and largest change per step, e.g. ±25 %. |
| Validity window | The mandate ends on a date; after that every call is forbidden. |
Set the mandate's end time to now, or remove the tool from it. The next call any agent makes on that account is forbidden, typically within seconds, because every call is checked. Pausing campaigns stays possible if your mandate allows update_campaign_state.
What MolTrust cannot stop: a call your code sends without the guard. The guard has to sit in the only path to Amazon; your engineering team decides that.
Each verdict carries a record that binds the mandate, the change and the result. Your client, your auditor or a court can recompute it with the open-source verifier, without MolTrust and without trusting MolTrust's word.