What happens if my AI agent's token is stolen?

#The question

With Swirls the damage is capped by design. Execution credentials are scoped to one run with a short expiry, so a stolen token cannot be replayed later and never grants more than that single run could already touch.

#Who's asking

Platform / infra engineer. Owns how things run in production. Cares about durability, isolation, audit, and repeatable deploys.

#Why Swirls is a fit

Every agent execution runs with its own identity. Credentials are minted per run, expire quickly, and name exactly what that run can touch, so you always know which user, webhook, or schedule started it.

Credentials only narrow. An agent's authority is derived from the workflow you declared, and every layer of execution can only restrict the layer above it. There is no path for an agent to escalate its own access.

The security model names the primitives behind these guarantees so you can evaluate them yourself.