How this YC Startup Secures AI Agents (Interview with Founder, Clam)
🔗 Link do vídeo: https://www.youtube.com/watch?v=KY9TBKdSfdk
🆔 ID do vídeo: KY9TBKdSfdk
📅 Publicado em: 2026-03-08T21:08:31Z
📺 Canal: Composio
⏱️ Duração (ISO): PT30M27S
⏱️ Duração formatada: 00:30:27
📊 Estatísticas:
– Views: 47
– Likes: 5
– Comentários: 1
🏷️ Tags:
Your AI agent has access to your Gmail. Your dad sends you his tax information. Now what?
That actually happened to Vaibhav Agrawal, founder of Clam (YC W26).
Julia sat down with Vaibhav to talk about how he's solving the security problem for AI agents—and why he integrated Composio in one night.
What happened:
Vaibhav's agent was scanning meeting invites for YC launch. His dad emailed tax information that same day. The agent nearly ingested every detail—SSNs, financials, all of it.
Thanks to Clam's semantic firewall, it never saw a thing.
What we covered:
• Why AI agents can't be trusted without security (it's a trust problem, not a tech problem)
• How CLAM's semantic firewall intercepts every request at the network layer
• Key swapping: Why AI agents never see real credentials
• The one-night Composio integration that gave CLAM access to 1,000+ tools
• Real security incident: How CLAM blocked sensitive tax info automatically
• Pivoting from hardware to AI agents in 2.5 weeks
• Who uses CLAM (engineering, sales, CS teams)
Why this matters:
AI agents need permissions to act on your behalf—accessing Gmail, LinkedIn, customer data. Without security, one prompt injection away from a data leak. CLAM makes AI agents safe with semantic firewalls, while Composio handles 1,000+ tools and integrations so CLAM can focus on what matters: keeping your data secure.
Vaibhav's words: "If another founder asked about using Composio? Do it. It's a no-brainer."
ABOUT COMPOSIO
Composio provides 1,000+ pre-built integrations for AI agents—so you can spend 45 minutes integrating instead of 5 weeks building.
Try Composio: https://composio.dev
FOLLOW VAIBHAV
Twitter: @vaibagra
Website: tryclam.com
FOLLOW COMPOSIO
Twitter: @composio
Website: composio.dev
ABOUT THIS SERIES
We interview founders building AI agents to understand what works in production, not just what sounds good in theory.
If you're building AI agents, subscribe for more conversations like this.
𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒
(00:00) Intro
(00:37) Meet the Founder
(00:54) What Clam Does
(01:47) Pivot to AI Agents
(05:13) Why Agent Security Matters
(07:08) Beyond VMs and Firewalls
(08:39) Semantic Firewall Explained
(10:28) What Gets Scanned
(11:30) Credential Key Swapping
(13:16) Real Incident Caught
(14:13) How Compo Fits In
(15:40) All Integrations Enabled
(16:24) Why Choose Compo
(17:43) Extra Security for Integrations
(18:55) End to End Email Flow
(20:23) The Story Behind Clam
(21:02) Time Saved vs Building In House
(24:38) Who Uses Clam Today
(26:41) Founder Recommendation
(27:53) Whats Next for Clam
(29:10) Final Advice for Builders
Have a question or ran into an issue?
Join our active community support here —
Discord server: https://dub.composio.dev/discord
Discord support channel: https://dub.composio.dev/slVwOmG