Speakeasy CEO Sagar Batchu uses a narrated production-deletion incident to explain why an agent’s access needs action-level controls.
Identity and authority
- Batchu describes an agent given a staging task that found an infrastructure token and deleted a production database and its backup. This is his reconstruction of an incident, not a demonstration of the original event.
- Give the agent its own identity and record both the operator and the person who authorized its credentials.
- Evaluate each request against the intersection of the credential’s ceiling, the agent’s policy and the responsible person’s current permissions.
- A staging-scoped agent should be unable to delete production even when its human operator could.
Enforce and record
- Route requests through a control point that can allow, deny, quarantine or escalate actions and record the decision.
- Secret detection in prompts is a separate safeguard from restricting what credentials can do.
- Controls only cover actions that actually pass through the enforcement point; direct credentials and bypass paths matter.
- Batchu describes Speakeasy’s product and says customers can use their own encryption keys or a data plane in their own cloud environment. These are vendor claims, not an independent security assessment.
“The agent had valid credentials but it didn’t have valid intent.” — Sagar Batchu