procedure
Grant and revoke an agent mandate
A named person authorises every action that commits money.
- steps
- 6
- things needed first
- 2
Free, with no card. We read your homepage, draft who buys from you and show your monthly price before you join the waitlist. Nothing is bought until you've approved the plan and the ads.
what you need
You need these before you start
- A workspace and the human permissions that gate consequential actions, which are issued from server-controlled roles
- A mission for the agent to work inside
the procedure
The procedure has six steps
Every step comes with a note on what commonly goes wrong there.
- step 01
Create a mission
A mission is a durable objective owned by your workspace. Everything the agent does happens inside one.
what goes wrong hereAgents cannot close their own missions. That is a human-only operation with no agent tool.
- step 02
Grant a mandate with an explicit ceiling
Enumerate the allowed actions, the currency, the validity window and the money ceiling. A mandate that does not name an action does not permit it.
what goes wrong hereSet the ceiling to what you are willing to lose rather than what you intend to spend. The budget itself is set in the plan.
- step 03
Let the agent prepare and propose
The agent works through ordered steps against the mandate, recording decisions and evidence as it goes. It can extract, compile, plan, draft creative and surface exceptions.
what goes wrong hereIt cannot enable spend. Approval records evidence; enabling spend on a staged live line is a separately granted action.
- step 04
Approve by exact digest
High-consequence work requires a single-use approval bound to an exact action digest. If the request that arrives does not match the bytes a human approved, it fails closed.
what goes wrong hereAn agent that tries to resolve its own approval receives a 403 response that requires a human. The API enforces this, whatever the tool metadata says.
- step 05
Resolve exceptions yourself
An ambiguous supplier outcome raises an exception, halts the run, and waits for an explicit human resolution and resume. It is never retried automatically.
what goes wrong hereThis is the failure this design exists to prevent: an agent that cannot read a supplier's response and tries again has just created a second campaign nobody knows about.
- step 06
Revoke when the work is done
Revoke the mandate rather than leaving it to expire. Revocation is a human-only signed action with no agent tool.
what goes wrong hereA secret-only credential rotation also advances the connection revision and revokes issued grants, which is worth knowing before you rotate a key mid-campaign.
An agent that can do useful work inside an explicit ceiling, and cannot reach any of the operations that commit money.
other procedures
You might need these procedures next
- Set an awareness budget from your market size
- Run a geo-lift test
- Connect your analytics
- Approve creative for UK clearance
- Connect Claude to your AdBuyMCP account
- Check a lawful-basis manifest
Talk your market and your plan through with James Rooney, who built AdBuyMCP and wrote its code.
These questions come up when you grant and revoke an agent mandate
What can an agent do that a human cannot undo?
Nothing that commits money. No agent tool exists for 11 consequential operations, which are human-only signed REST actions, among them approvals, provider-attempt resolution, mandate replacement and revocation, mission closure, workflow acknowledgement, asset-job resolution, dossier saving and verification, and issuing or revoking a live execution grant. What an agent can do is prepare, propose, draft and surface, all of it recorded. The design intent is that an agent removes work rather than removing accountability.