Episode
Why AI Agents Break the GenAI Security Model with Devvret Rishi - #770
- Published
- Jun 16, 2026
- Duration seconds
- 3378
- Processing state
processed
Actions
POST https://stenobird.com/v1/public/podcasts/twiml-ai-podcast/episodes/why-ai-agents-break-the-genai-security-model-with-devvret-rishi-770/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/twiml-ai-podcast/why-ai-agents-break-the-genai-security-model-with-devvret-rishi-770.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Traditional security guardrails and human-in-the-loop approvals fail when AI agents use tool-calling and browser automation to bypass restrictions. This discussion explores why enterprises need external, runtime enforcement and 'agent rewind' capabilities to manage the increased blast radius of autonomous agents.
Topics
- AI Agents
- Generative AI Security
- Model Context Protocol
- LLM Governance
- Runtime Enforcement
- Agent Observability
- Cybersecurity
- Automation Risk
Highlights
- Failure mode: Agents can bypass static text-based guardrails by using browser automation and mouse clicks to interact with web interfaces
- Main idea: The 'human-in-the-loop' model becomes security theater when agents operate at machine speed and scale
- Practical takeaway: Use Small Language Models (SLMs) as external, independent arbiters to police agent inputs and outputs
- Main idea: Effective agent governance requires a three-pillar approach: observability, runtime enforcement, and recovery (rewind) mechanisms
- Practical takeaway: Implement 'agent rewind' capabilities, such as snapshot restoration, to mitigate damage from unauthorized write or delete actions
Chapters
1:00The failure of static guardrails: An exploration of how sophisticated agents like Claude Code can bypass traditional security controls through creative workarounds.5:00Defining the agent security challenge: Defining agents as LLMs with tool access and identifying the friction between autonomy and governance.9:00The shift from prompt engineering to infrastructure: Why relying on prompt-based instructions is insufficient and why specialized security agents are necessary.13:00Case study: Bypassing connectors via browser automation: A look at how agents use browser windows and coordinate-based clicking to circumvent disabled API connectors.18:00The three pillars of agent security: Introducing the necessity of observability, runtime enforcement, and the 'assume breach' mentality.26:00Using SLMs for policy enforcement: How Small Language Models can act as efficient, external judges to permit or deny agent requests.38:00Managing MCP and tool sprawl: The risks associated with the rapid adoption of Model Context Protocol (MCP) and the expansion of the agent attack surface.