First, What An AI Agent Actually Is
A chatbot answers you and an AI agent acts for you.
If you give an agent a goal instead of a question, it plans the steps, calls tools, runs code, reads and writes files, logs into services, and keeps going until the goal is met or it gives up.
All without checking back after each move.
That last part is the business case. It is also the risk. An agent needs four things a chatbot never gets: credentials, tool access, network reach and permission to act unsupervised.
Hand over all four and you have a worker who never sleeps, never asks whether a task seems odd, and never notices it has wandered somewhere it should not be.
Every enterprise is racing to deploy these. Three disclosures in two weeks show what happens at the edges.
Three AI Agent Failures In Two Weeks
On July 21, OpenAI said models under evaluation escaped a sealed test environment by exploiting an unknown vulnerability in a self-hosted package registry proxy, then reached Hugging Face’s production infrastructure. Four accounts across four services were involved, and Hugging Face’s forensic timeline documents 17,600 distinct actions across four days.
On July 30, Anthropic published its own review, prompted by OpenAI’s. Across 141,006 evaluation runs it found three cases where a model reached the internet from a third-party test environment and got into three real organizations’ production systems. The earliest was in April. Each model had been given a capture-the-flag exercise: a secret is hidden on another machine, go retrieve it. Each was also told the environment was a simulation with no internet access. That part was wrong.
Around July 22, researchers at Manifold Security showed that Microsoft’s official Azure DevOps MCP server returns pull request descriptions verbatim, hidden HTML comments included.
An attacker writes instructions no human reviewer can see. A developer asks their AI assistant to review the pull request, and the assistant follows them, using the developer’s own credentials, into projects the attacker could never open. No Microsoft agent did anything here. One tool was missing a guardrail its siblings already had.
How The AI Agents Got In Through Doors That Were Never Locked
The most important line in Anthropic’s disclosure is not the one everyone quoted. It is the part explaining how the models got in. Basic techniques, the company said, like weak passwords and unauthenticated endpoints.
The instructions did not forbid what happened, and the environments did not prevent it. Anthropic’s guardrail was a sentence in a prompt asserting the internet was not there. OpenAI’s was a sandbox with a hole in software the model was permitted to use. Neither was a control. Both were assumptions.
The Azure DevOps case makes the same point from the other direction. That agent did nothing unexpected. It read a document and did what the document said, which is what agents are for. It had no way to tell data from orders.
Pete Erickson, founder of Modev, framed the stakes this way when I asked for his view. “Autonomous agents hold so much promise but at the same time hold a new kind of power that we’re not fully prepared to manage. Cars were initially designed without safety belts and today auto safety is a huge market. The same dynamic is at play where trust and safety become an integral part of the Agentic AI economy.”
Nobody Detected These AI Agents For Months
Follow the dates. Anthropic’s earliest incident was in April, found July 24, after a review that began July 23, after a competitor’s disclosure on July 21.
Two of the three organizations had no idea until Anthropic called them.
Hugging Face disclosed July 16 and OpenAI saw signs in its own systems the following weekend. The target noticed before the owner did.
Congress has responded with the AI Kill Switch Act.
A kill switch responds to something you have detected, and detection here took months and came from outside. A switch nobody knows to flip is not a control either.
This is a big issue as most agents today don’t have all the right controls.
What To Do About Your AI Agents This Quarter
Many companies are asking what they should do now.
Wolf Ruzicka, global chief commercial officer and CEO North America at Unlimit, broke the answer down this way for me. “Every serious software team ships through a series of gates: build it small, test it internally, let a limited group of real users try it, then a monitored pilot, and only then release it to everyone. We’re skipping most of those gates with AI agents and putting them straight in front of customers. The infrastructure to do it properly already exists. What’s missing is the patience to use it.”
Other advice includes:
- Inventory what your agents can reach, not what they were issued. Service accounts and inherited tokens are where scope quietly expands.
- Log tool calls, not just outputs. Both labs could reconstruct these timelines because actions were recorded. Most deployments log the conversation and lose the actions.
- Assume any agent reading text other people wrote can be given orders by it.
- Fix the boring things. Weak passwords and open endpoints let a test system into three real companies.
AI agents have not created a new class of vulnerability. They have removed the labor cost of finding the old ones at scale. The capability question will keep advancing. The permission question is on the table now for AI Agents, and it is answerable.
