

Your team is probably deploying AI agents right now. The harder question is what those agents can reach once they're running. In episode 82 of The STEMINISTS Podcast, "Your AI Agent Just Became a Security Risk. Now what?", hosts Phoebe Goh and Darnell Fatigati chat with Sandra Dunbar, the NetApp® lead for cyber resilience product marketing. Sandra's answer is practical, and it stuck with me: the future of AI security isn't about trusting agents more. It's about trusting them less, intelligently.

A person might make one bad call. An agent can make the same one thousands of times—in seconds. Sandra explores what that speed changes, why we should assume compromise, and where an emergency stop fits in.
The Model Context Protocol (MCP) standardizes how agents connect to tools and data. That convenience creates a high-value trust boundary, and you need to secure it on purpose. In Sandra Dunbar's words, "MCP gives agents a doorway into your tools and your data, and the security challenge is making sure that that doorway doesn't become a shortcut to your existing control."
Yes, and Sandra argues it applies more strictly than it does for people. Every agent needs an identity, permissions, monitoring, and accountability, the same as any employee or application. She describes a layered approach:
Even strong controls have limits. When an agent crosses a boundary, immutable, isolated data copies can provide a route back. But what does effective recovery look like when AI mistakes happen at machine speed?
Perhaps more than you'd think. Sandra draws a surprisingly apt connection between raising an independent teenager and managing AI agents: freedom works best when it expands gradually, within clear boundaries.
Her analogy gets even more interesting when friends—or additional agents—enter the picture. Listen to the episode to hear why managing a group of overconfident teenagers might be useful preparation for securing multiagent systems.
I encourage you to listen to the full conversation. Phoebe, Darnell, and Sandra cover all of this in under 15 minutes. Listen to episode 82 of The STEMINISTS Podcast and follow the show so you catch every new episode. Leave a review or connect with Darnell Fatigati and Phoebe Goh on LinkedIn.
Learn how to secure data, reduce risk, and recover quickly from attacks with an infrastructure architected for resilience.
What is the biggest security risk with AI agents?
The biggest security risk with AI agents is excessive access, not malicious intent. In this STEMINISTS episode, NetApp’s Sandra Dunbar explains that a well-intentioned agent with broad permissions and weak guardrails can cause significant damage because it acts at machine speed without human judgment.AI agents act at machine speed without human judgement, so a single bad decision can repeat thousands of times in seconds.
Does zero trust apply to AI agents?
Yes, zero trust applies to AI agents. Each AI agents need an identity, permissions, monitoring, and accountability, with identity verification and monitoring should be even stricter than for human users.
How should enterprises apply zero trust to AI agents?
Enterprises should apply zero trust to AI agents through layered controls that limit what each agent can reach and watch what it does. Sandra Dunbar of NetApp outlines five layers:
What is the Model Context Protocol (MCP) and why does it matter for security?
The Model Context Protocol (MCP) is a standard that defines how AI agents connect to tools and data. That makes it a high-value trust boundary, so organizations need to secure it explicitly. Without identity verification and least-privilege access at the MCP layer, an AI agent can bypass the controls you already have in place.
How do you recover from an AI agent mistake?
You recover from an AI agent mistake by restoring from immutable, isolated copies of your data. They give you a recovery path when an agent deletes or changes something it shouldn't. Zero trust controls reduce risk, but they can still fail. When an AI agent deletes or changes data it shouldn't, immutable, isolated data copies give you a clean path back.