Topic starter
11/10/2026 6:56 pm
TL;DR: Most organisations do not know how many AI agents are running because agents arrive through package installs and leave only host artifacts, according to Visiq Labs, so discovery has to scan fleets for framework packages, MCP server manifests, local runtimes, and tool configurations.
Editorial analysis by NHI Mgmt Group, based on content published by Visiq Labs: “Finding the agents nobody told security about”.
Key questions
Q: What breaks when AI agents are discovered too late or not at all?
A: When agents are not discovered early, teams cannot assign ownership, set scope, or prove what systems the agent can reach.
Q: Why do hidden AI tools create a governance risk beyond ordinary software sprawl?
A: Hidden AI tools can process sensitive data, call external services, and change outputs or decisions without leaving a clear ownership trail.
Q: How do you know if AI discovery is actually working?
A: AI discovery is working when the organisation can produce one authoritative inventory, classify tools consistently, and explain which data and permissions each tool can reach.
Practitioner guidance
- Build host-based AI agent discovery Scan endpoints and workloads for framework packages, local model runtimes, MCP server manifests, and tool configuration files rather than waiting for self-reporting.
- Treat agent inventory as a governance register Record each discovered agentic framework, runtime, and MCP server as a governed identity asset with an owner, environment, and authorised purpose.
- Enforce tenant-scoped discovery boundaries Define which fleets may be scanned, approve those scopes explicitly, and prevent discovery tooling from extending beyond owned environments.
Bottom line: AI agent discovery is a prerequisite for governance because self-reporting is not reliable enough to support inventory, ownership, or authorisation.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/10/2026 6:57 pm
Agent discovery is now a governance prerequisite, not an optional hygiene task. If you cannot enumerate AI agents, you cannot decide who or what is authorised to act through them. The article’s core point is that agentic software often bypasses procurement and therefore bypasses the normal identity register, which means the first failure is governance blindness. Practitioners should treat discovery as the front door to agent control.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should organisations do when discovery finds an unapproved MCP server or local model runtime?
A: Treat it as an unmanaged authority path until an owner, environment scope, and business purpose are confirmed. If those cannot be established quickly, isolate the component and remove its access to tools or data before it becomes a standing control exception.
👉 Read our full editorial: Agent discovery is the first control for governing AI agents