· ai-devtools

How one AI agent exposed five critical enterprise security gaps

Imagine an AI agent being created.


Not by an identity team, nor by a security professional. This one is built by someone in accounts at a mid-sized company.

The agent's job is relatively simple: read an inbox, match invoices against the ERP, and post a daily summary to Slack. And since a frontier model was used to build it, it's a one-shot, 10-minute task.

Nobody in security knows the agent exists. In a survey of 418 IT and security professionals commissioned by Token from the Cloud Security Alliance in January 2026, 68% reported having strong visibility into their AI agents.

Yet 82% had found agents they didn't know about in the past year. The evolution of agents is so rapid that the security playbooks are being written on the go.

The people responsible for agent security need to figure things out in production, one problem at a time. At Token Security, we asked more than 20 of them to write down what they've learned for the Agentic Universe, a free learning hub. Below, we follow this one agent from the afternoon it was built to the audit after it went wrong, and stop at five points where one of those practitioners could have changed the outcome.

Earlier coverage

Related coverage

Also worth reading

  1. next.js 16.5.0-canary.50 released
  2. Daemons can now send traces to Vercel Tracing
  3. Anthropic now lets you self-host Claude Managed Agents. The catch? 8 hours to act if it flags a safety risk
  4. This year’s bug count just passed 100K
  5. Amazon Threat Intelligence observes threat actors running cybercrime campaigns with ARTEX AI agents