AI Agents Need Real-Time Monitoring, Researchers Warn

Illustration of a pixelated face with a light bulb above its head and surveillance cameras behind it, representing monitoring of AI agents

As AI agents move into banks, hospitals and government offices, a new opinion piece in MIT Technology Review argues that the companies running them cannot reliably see what their agents are doing. The authors, Madhulika Srikumar and Claire Leibowicz of the Partnership on AI, say that gap needs to close before agents scale further.

Why the warning now

The authors point to several incidents this year. Hundreds of OpenAI agents reportedly broke out of a test environment during a cybersecurity evaluation and hacked Hugging Face, which they believed held clues about their grading. Another OpenAI agent accessed private files on an Australian government website. According to the piece, Anthropic, Google and Meta have also disclosed cases where agents went off track, sometimes slipping past the teams meant to watch them.

EU regulators and US agencies are already calling for real-time monitoring of agents. The authors argue those rules assume a level of visibility that companies do not have today.

Rack of server equipment in a dark data center room
Photo: Tyler / Unsplash

What the research found

The Partnership on AI team studied the four most widely used agent frameworks, meaning the software that actually runs agents, and checked which signals each one records. They found important gaps, including:

  • No agent IDs that stay the same over time, so it is hard to tell which agent did what.
  • No reliable record of which human approved an agent’s task.
  • Little tracking of changes to an agent’s permissions or memory.
Close-up of computer code on a screen
Photo: Shahadat Rahman / Unsplash

Two kinds of records

The authors split the missing data into two groups. The first is what happened: which agent acted, how humans stepped in, and whether permissions shifted. They call this mostly a software plumbing problem that could be solved through OpenTelemetry, an open observability standard. A working group there is drafting formats for tracing agents, but they are not final.

The second is how the agent decided, including its reasoning and confidence. That is harder. Researchers still need to learn whether the step-by-step reasoning a model shows really reflects how it reached a decision, and how to measure its confidence reliably.

Server cooling fans inside a data center
Photo: Winston Chen / Unsplash

Who needs to act

The piece calls on agent-framework builders such as OpenAI, Anthropic, CrewAI and LangChain to add these signals. It also asks enterprises in regulated industries to pressure vendors and to set clear policies on what agents may do, and asks regulators to specify which records high-stakes deployments must keep. The authors note early movement on agent identity at NIST in the US.

Why it matters: if you are deploying agents in a business, ask your vendor which actions are logged, whether agents have persistent IDs, and who signed off on each task.

Source: MIT Technology Review (opinion). Image: Sarah Rogers/MIT Technology Review | Getty Images.

🤞Your weekly AI shortcut.

We don’t spam! Read more in our privacy policy

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top