Supervising-agent service running policy separate from worker agents
A separate supervising agent — one that does no work itself but decides what the worker agents may do — sold as an independent, pluggable component. A protocol boundary between supervisor and worker lets users swap either piece instead of the agent vendor deciding the guardrails.
online B2B Deep Tech / Infrastructure
From AI Engineer — An AI Agent Got Its User Banned From Resy — Keycard, JPMorgan Chase & AAuth at 11:19
Problem: Agents and their vendors currently decide their own guardrails; human-in-the-loop approval does not scale and causes consent fatigue, so control over what agents can do needs to live in a component the owner controls.
For: Individuals and organizations running many agents whose volume makes human approval of every action impossible.
Products from this video
Examples
- The web's federated-protocol precedent — OIDC, TLS — as the model for open agent-authorization rails versus walled-garden personal-agent protocol efforts.
Other takes on AI security infrastructure
- 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
- Privacy-first document preprocessing layer for AI coding agents