# How to Detect Shadow AI Across Networks, Endpoints, and MCP

URL: https://3ammarketer.com/blog/how-to-detect-shadow-ai
Published: 2026-10-22

> A tactical guide to discovering unsanctioned AI tools across network egress, local developer runtimes, and background Model Context Protocol connections.

Detecting shadow AI requires auditing outbound network traffic, scanning developer machines, and inspecting background Model Context Protocol (MCP) agent connections. Security teams cannot rely strictly on SaaS discovery tools when employees run open-weight engines locally or connect unapproved coding assistants to internal codebases. [1][2][3]

The scope of unauthorized artificial intelligence expands rapidly across corporate infrastructure. A 2026 Netskope study found that 92% of organizations have employees accessing unsanctioned AI services through corporate networks. Furthermore, half of enterprises operate at least one shadow AI application, and 51% of employees report connecting AI tools to enterprise systems or applications without IT authorization. [2][4][5]

Enterprise shadow AI exposure and unsanctioned tool usage rates reported in 2026 enterprise studies, in percent. [2][4][5]

- Orgs with unsanctioned AI access: 92 %
- Employees connecting AI without IT: 51 %
- Enterprises with shadow AI apps: 50 %

The operational risks carry severe financial liabilities. The average cost of security incidents in organizations with a high level of shadow AI usage can reach $670k. Data leaks remain frequent: approximately 10% of generative AI prompts contain corporate intellectual property or sensitive corporate data, and Obsidian observed over 10,000 routing numbers entered directly into AI prompts across customer environments within a few months. [2][4][5]

## Intercepting frontier API endpoints and DNS queries

Outbound network traffic analysis provides direct visibility into unsanctioned cloud interactions. Network inspection rules must actively monitor outbound traffic to known AI service endpoints, including api.openai.com, anthropic.com, bard.google.com, and copilot.github.com. Evaluating DNS query logs captures attempts to contact frontier model backends from internal workstations before payloads resolve. [2][3]

Frontier models accessed via custom wrappers often obscure data leaks. A documented database leak involving DeepSeek exposed 1 million sensitive entries, underscoring the exposure risk when internal documents flow into third-party providers. [4][9]

## Identifying local runtimes like Ollama via port scans

Developer workstations frequently bypass cloud boundary firewalls by executing open-weight architectures on bare metal. To locate ungoverned instances of local runtimes, detection engineers deploy targeted internal port scans paired with API dummy queries to expose services such as Ollama, LM Studio, and llama.cpp running on developer hardware. [3]

Teams managing [local AI models](/blog/local-ai-models-guide) often host internal inference daemons that accept raw payloads without authentication. Probing local loops using network mapping tools like nmap allows security operators to flag active listeners serving standard completion endpoints. Once an open port is flagged, sending a standardized API dummy query verifies whether the service exposes a local language model daemon. [3]

## Uncovering ungoverned MCP servers and developer coding skills

Developer environments represent a primary vector for ungoverned automation. In a 2025 Stack Overflow survey, 42% of developers admitted to using unsanctioned AI coding assistants at work. Developers routinely introduce skills, plugins, and MCP servers via channels such as Git, Slack, marketplaces, or zip files outside central security reviews. [2][6]

Malicious packages and ungoverned AI assets increased by 7.4 times over the course of three years. The JFrog 2026 Software Supply Chain Security report tracked malicious agent skills, identifying 969 carrying high-impact payloads alongside 495 malicious models on Hugging Face. Despite these threats, four out of five enterprises lack a governance framework to monitor and manage their coding agents. [6][7]

Identified malicious AI agent skills versus malicious Hugging Face models tracked in the JFrog 2026 report. [6]

- Malicious agent skills: 969
- Malicious models: 495

To close this visibility gap, JFrog AI Security introduced Local Shadow AI Detection for Unified Security and Ultimate Security customers. Deployed through the JFrog Agent Plugin on developer workstations via mobile device management (MDM) or agent harness settings, it finds skills, plugins, and MCP servers directly on employee endpoints where pipeline and registry controls do not reach. The harness returns only metadata and risk assessments to the central management platform without transmitting proprietary code off-device, supporting model scanning for Anthropic Opus 4.8, OpenAI GPT 5.6 Sol, and Google Gemini 3.1 Pro. [6]

## Tracking protocol-level agent traffic across STDIO and Streamable HTTP transports

Autonomous developer workflows introduce autonomous agent layers via the Model Context Protocol. MCP implements a JSON-RPC 2.0 based exchange protocol defining message structures and semantics. MCP tools are executable functions that AI applications can invoke to perform operations like file actions, API calls, and database queries. Crucially, these shadow AI agents often possess permissions to summarize, send, update, or alter data across connected applications and APIs outside organizational control. [1][8]

Visual Studio Code functions as an MCP host and instantiates dedicated MCP client objects to maintain server connections. Monitoring these interactions requires understanding the underlying transport mechanisms. MCP servers operate locally using the STDIO transport or remotely via the Streamable HTTP transport. Security teams can detect remote Streamable HTTP traffic by monitoring outbound HTTP POST and Server-Sent Events traffic across proxy and network inspection boundaries, whereas local STDIO agent sessions produce zero network overhead and require endpoint process monitoring to detect unauthorized parent-child process invocations. [1]

## Sources

1. [Architecture overview - Model Context Protocol](https://modelcontextprotocol.io/docs/concepts/architecture)
2. [Shadow AI: Detect & Manage Unauthorized AI Tools | Workers Delos](https://delos.so/blog/shadow-ai-enterprise-detection-management)
3. [Building a ShadowAI detection tool, need inputs from the community : r/cybersecurity](https://www.reddit.com/r/cybersecurity/comments/1la3gc8/building_a_shadowai_detection_tool_need_inputs/)
4. [Shadow AI Security: Find and Govern Every AI Tool](https://www.obsidiansecurity.com/shadow-ai-security)
5. [Shadow AI Detection: The First Step Toward Securing AI](https://www.darktrace.com/blog/shadow-ai-detection-the-first-step-toward-securing-ai)
6. [JFrog Closes the Shadow AI Blind Spot: Unveils AI-SEC to Control Every AI Agent, Skill, and Model, from Developer to Production](https://www.innovationopenlab.com/news-biz/74027/jfrog-closes-the-shadow-ai-blind-spot-unveils-ai-sec-to-control-every-ai-agent-skill-and-model-from-developer-to-production.html)
7. [JFrog introduces AI-Generated Code Detection and Shadow AI Detection | DevOps.com posted on the topic | LinkedIn](https://www.linkedin.com/posts/devops-com_jfrog-adds-ability-to-track-usage-of-ai-coding-activity-7395066614070644736-qb4O)
8. [How to Detect and Govern Shadow AI in Your Organization](https://nordlayer.com/blog/shadow-ai-detection/)
9. [LLM API pricing timeline (3AM Marketer data set)](https://3ammarketer.com/data/model-pricing)
