The agent asks. The policy decides. A human signs.
An AI agent got a Black Friday brief for 8 EU markets and made 28 calls to Campaign. The gate ran 13, explained 1 without running it, sent 5 to a human, and blocked 9 before they reached production.
How a tool call travels
Adobe’s CX Enterprise agentic tools list Campaign Classic capabilities that include query execution, workflow control and SOAP/JS execution [1]. The gate is an MCP server the agent talks to instead. Approvals are not a tool the agent can call.
Loosen a rule and watch the same session play out
Every change re-runs all 28 agent calls through the gate in your browser. Simulated approvers sign whatever reaches them, except the production reminder they reject for a business reason. That is the point: humans alone miss what policy catches.
Policy
Submit your own call to the gate
Write SQL or server-side JavaScript, request a send or a workflow action. The gate uses whatever policy is set in the lab, and every decision is hashed into a live audit chain.
Approval inbox
Requests waiting for a person. Approve as different roles to see role checks, dual sign-off and the re-check at execution time.
Live audit chain
SHA-256 of each entry includes the previous hash, computed in your browser.
Four of eight markets would have shipped a defect
Checks follow Adobe’s own pre-send guidance [3][4][5][7][8]. Select any cell for the detail. Apply a fix and the lab and playground re-run against the corrected delivery.
Forge any entry and the chain gives it away
The recorded session wrote 34 entries, blocked calls included. Select an entry to rewrite its decision, as someone hiding a mistake might. Every entry after it stops verifying.
Rules live in a reviewed file, not in a prompt
This file follows the lab. Lines you changed are highlighted.
- 01Fail closedA tool not in the policy is blocked. New capabilities are opt-in.
- 02Anything that looks like a write is a writePattern analyzers over-block on purpose. A false positive costs one click; a false negative costs a market.
- 03Re-check at execution timeIf a proof is withdrawn while a send waits for sign-off, the approved send is still stopped.
- 04Separation of dutiesRole-checked approvers, two people above a volume threshold, nobody approves twice.
- 05Defence in depthOperator groups and named rights stay the outer wall [6]. The gate adds intent checks those rights cannot express.
Grounded in Adobe Experience League
Adobe’s documentation names the capabilities and the checks. Where it is silent, such as which agent capabilities are read-only, the gate assumes the worst case.