Customer data glossary

Blast radius (AI agents)

Blast radius is the most harm one AI agent run can do if it goes wrong, measured in records changed, messages sent, money spent or destinations reached, and capped by limits set outside the model.

By Art Kukharenko · Published · Updated

All glossary terms

Part of the Learn hub and the customer data glossary.

What it means in practice

Blast radius sizes a failure before it happens, and it has two parts: how much a run can touch and whether the result can be undone.

The idea comes from reliability engineering. AWS describes cell-based designs that limit a failure's scope: with 10 cells serving 100 requests, a failure leaves 90% of requests unaffected 1.

On a rail card, blast radius sits in the Limits field: maximum records, maximum sends, budget, rate, time window and allowed destinations. A gateway or execution service holds these limits, because a limit inside a prompt is only a request.

The radius can grow in two ways. Agents acting in chains can cause what OWASP lists as cascading failures 2, so set combined limits across rails. Effects can also land outside your systems: Amazon SES may review an account at a 5% bounce rate and may pause sending at 10% 3. See 7 things AI agents should never do.

PrivyCDP lets teams restrict what data its AI reaches, which narrows one part of the radius.

Example (online retailer, illustrative): the Audience Sync Steward runs at L3. Its worst case is a wrong audience sent to one allow-listed destination, up to a maximum size, with a limit on syncs per day. Above a size threshold, a second approver must sign.

Where it matters

Back to the customer data glossary or the Learn hub.

Browse use casesFunction playbooksAgent roster

FAQ

How do you limit an agent's blast radius?

Cap records, sends, spend, rate and destinations in a system outside the model. No universal number exists, so start from the size of a normal run and the cost of one wrong action.

Is blast radius the same as risk?

No. Risk also includes how likely a failure is. Blast radius assumes the failure has happened and asks how far it reaches, so you can bound it even when the likelihood is unknown.

Sources

  1. AWS Well-Architected Framework, bulkhead architectures
  2. OWASP Top 10 for Agentic Applications for 2026
  3. Amazon SES, enforcement FAQ

Further reading

Published: · Updated:

Editorial dates describe content changes. Confirm current sources before making legal, security or purchasing decisions.