Back to Feed
AI SecuritySep 26, 2026

Zero Trust for AI Agents Starts With Fixing Zero Visibility

AI agents lack visibility, creating shadow IT risks and enabling attacks like the METR incident.

Organizations are deploying AI agents without adequate visibility or oversight, leading to shadow IT risks and potential security incidents. A recent attack on METR, stemming from an unmonitored AI agent, highlights the dangers of unconstrained API key usage and the lack of spending limits. Applying Zero Trust principles requires establishing inventory and visibility before implementing enforcement controls.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run Hugging Face?

Get an email when a new story names Hugging Face, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

Organizations are rushing to deploy AI agents without first establishing the foundational visibility required to govern them safely, effectively creating a new wave of shadow IT. The attack on METR demonstrated that unmonitored AI agents with unconstrained API keys can act autonomously in ways that cause real security incidents and financial exposure. Without an inventory of what AI agents exist, what permissions they hold, and what actions they are taking, Zero Trust enforcement is impossible to implement. This matters because AI agents can generate API calls, consume resources, and exfiltrate data at machine speed — far faster than human-driven threats. Visibility and inventory are not optional prerequisites; they are the foundational controls from which all other AI governance must follow.

What helps against this

How we list vendors

Indicators of Compromise

Extracted by AI from the linked source. Not reviewed by an editor. How this works

  • malware — vibe-coded agentic app

Entities

OpenAI agents (product)AWS (product)Azure (product)Hugging Face (vendor)Veeam (vendor)attacker (threat_actor)