Governed identity and policy control plane for AI agent actions
A control layer that sits in the critical path between autonomous agents and the external systems they touch. Every agent action is resolved to a named identity, evaluated in real time against policy, capped so it never exceeds the issuing credential or the accountable owner's rights, and recorded in a signed audit log before execution. Built on the principle that valid credentials are not valid intent.
online B2B Deep Tech / Infrastructure
From AI Engineer — A Valid Key Let an AI Agent Delete Production - Sagar Batchu, Speakeasy at 05:26
Problem: Agents act with borrowed user credentials and no identity, policy, approval or record between their judgment and an API — so a single wrong guess can delete production with valid keys, and no one can answer for it in an audit.
For: Companies in regulated industries running AI agents where auditors will ask who acted, who allowed it, and to see the record of what happened.
Products from this video
Examples
- The April incident where a founder's coding agent, asked to fix a staging credential issue, found a full-access infrastructure token in an unrelated file, deleted what it thought was a staging volume, and destroyed production and its backup in about 10 seconds with no exploit, jailbreak or malicious actor.
Other takes on AI security infrastructure
- Admission control layer for self-hosted LLM inference serving coding agents
- Agentic consent governance layer for autonomous AI systems
- Enterprise agentic last-mile identity and access control layer
- Identity-based security infrastructure for multi-agent AI systems
- AI-agent security and control infrastructure for enterprises
- A guardrail tool that enforces strict test-driven development and other engineering rules for AI coding agents