Unique Customer Cap
Limit how many different customers an AI agent can open in a time window. Unique Customer Cap denies the next new customer once the count is full.
Real-Time(Preventive)Checked before the call runs, so it can stop it
A support agent looks up customers by customer.id. If it starts opening far more customers than a person at a desk would, something is wrong. This policy counts distinct customers in a window and denies the next new one once you hit your limit.
Runs On
The SDK only
You Set
How many distinct customers are allowed, and the time window in minutes.
Your Agent Sends
customer.id in the lookup arguments
What Happens
| Lookup | Cap of 2, with Block on |
|---|---|
| The first new customer | Runs. The customer is counted. |
| That same customer again | Runs. The count does not grow. |
| A second new customer | Runs. |
| A third new customer | Denied. |
| The arguments have no customer id | The rule is skipped and the lookup runs. The match is recorded as a warning. |
Set It Up
- In the app, open Policies and click Create Policy.
- Choose Unique Customer Cap.
- Set Max Distinct Customers and Window (Minutes), for example 30 customers in 60 minutes.
- Set the mode to Block, then click Activate Policy.
Workspace scope shares one count across agents on that policy. Agent scope keeps a count for that policy only.
What Your Agent Sends
Pass customer.id on the lookup arguments. Traccia hashes the id before storing it, so the Decision Log never shows the raw id. See the code.
Good To Know
- This is not a login system, and it is not a cap on how many calls one customer can make.
- This policy does not apply on the Gateway.
Next Steps
© 2026 Traccia.