Please ensure Javascript is enabled for purposes of website accessibility

Company News

The AI Security Crisis Hiding in Plain Sight: Why We Built Shadow AI Discovery

September 11, 2025

·

5-Minute Read

Table of contents

The Shadow AI RevolutionWhy We Had to ActIntroducing Shadow AI DiscoveryComplete DiscoveryIdentity MappingLegitimacy VerificationRisk AssessmentPolicy EnforcementWhy This Matters NowWhat's Next

Share Article

Over the past six months, I've noticed a troubling pattern in our customer conversations. CISOs are describing a new blind spot in their security posture: agentic AI development tools running on developer machines that they can't see, inventory, or control.

IAM leaders are equally concerned, but from a different angle. "We're tasked with securing machine identities we can't even know exist," one IAM director at a Fortune 500 company told me recently. "These identities are being consumed by dubious, third-party tools that aren't part of our approved software catalog - tools we can't audit or trust. The challenge of non-human identity management just got 10x harder with the advent of AI."

The symptoms are consistent across many organizations. Connections to AI services that aren't on approved vendor lists. Data access patterns that don't match any authorized workflows.

What they're seeing is the emergence of Shadow AI infrastructure, and it's happening faster than most security teams realize.

The Shadow AI Revolution

Here's what's really happening in many enterprises right now: while they craft AI governance policies in boardrooms, their developers are already building the future. They're installing Model Context Protocol (MCP) servers - the infrastructure that powers AI agents to read files, query databases, access APIs, and interact with virtually any system that has credentials.

This rapid adoption is driven by an incredibly low barrier to entry. Unlike enterprise AI initiatives that go through cloud-native platforms like AWS Bedrock or Google Vertex AI, where security teams are part of the conversation from day one - MCP tools require nothing more than a developer downloading, forking, or cloning a publicly available repository from GitHub. There's no procurement process, no security review, and no approval workflow. Just git clone and go.

These tools are incredible for productivity. They're accelerating development velocity by 25%+ in organizations that embrace them. But from a security perspective, they represent a completely new attack surface.

Consider the scale: you have thousands of developers, each potentially running multiple AI agents powered by MCP servers on their local machines. These servers have access to AWS keys, database passwords, API tokens - essentially, the keys to your digital kingdom. And most enterprises have zero visibility into what's running, what it's accessing, or whether it's even legitimate.

This isn't theoretical. Last month, we worked with a financial services customer who worked with us as a design partner on this new capability. We discovered 847 unknown MCP servers across their developer environment. Seventeen of those were accessing production databases. One showed suspicious connection patterns and is still under investigation.

The concerning part in all of this, is that their traditional security stack saw nothing unusual. Their EDR, SIEM, and DLP tools all classified these as legitimate developer software, which, in most cases, they are.

Why We Had to Act

At Clutch, we've built our entire platform around the premise that non-human identities are the new attack surface. Service accounts, API keys, secrets - these are the credentials attackers really want because they provide persistent, privileged access without human oversight.

MCP servers represent the evolution of this threat. They're not just accessing non-human identities; they're proliferating them, consuming them, and in some cases, potentially exfiltrating them, all while operating completely outside traditional security controls.

When we started seeing this pattern across our customer base, we had a choice: wait for the industry to recognize this threat, or get ahead of it.

So we chose to lead.

Introducing Shadow AI Discovery

Earlier this week, we announced Shadow AI Discovery, the first solution designed to provide complete visibility and governance over ungoverned Model Context Protocol servers in enterprise environments.

Here's what it does:

Complete Discovery

Automatically detects all MCP servers running across your developer environment, regardless of how they were installed or configured.

Identity Mapping

Shows exactly what credentials, tokens, and secrets each MCP server is accessing, extending our Identity Lineage™ technology to the AI development layer.

Legitimacy Verification

Distinguishes between official MCP servers and potential malicious imposters using behavioral analysis and threat intelligence.

Risk Assessment

Provides real-time risk scoring based on what data each server can access, how it's being used, and whether its behavior matches expected patterns.

Policy Enforcement

Enables organizations to set governance policies around MCP usage without killing innovation.

The solution integrates seamlessly with our existing platform - same zero-knowledge architecture, same API-first approach, same focus on enabling rather than blocking development velocity.

Why This Matters Now

I've been in cybersecurity long enough to recognize inflection points. The cloud migration created one around service accounts and API keys. DevOps created another around CI/CD secrets. Now agentic AI development is creating the next one around local developer tooling.

The enterprises that get ahead of this trend will have a massive competitive advantage. They'll be able to embrace agentic AI development tools safely while their competitors either block innovation or accept dangerous exposure.

But the window is closing fast. MCP adoption is accelerating, and once these tools become entrenched in developer workflows, retrofitting security becomes exponentially harder.

What's Next

This week, we started rolling out Shadow AI Discovery to existing Clutch customers. If you're not a customer yet but recognize this problem in your environment, please reach out.

This capability is the beginning of preventing what I believe will be the next wave of major enterprise breaches. The attack vectors are already there. The tools are already deployed. And the only question in my opinion is whether security teams will have visibility before the inevitable end up happening.

We've built the most comprehensive non-human identity security platform in the market. Shadow AI Discovery represents the natural evolution of that mission - extending our vision of identity governance to every corner of the enterprise, including the AI-powered future that's already here.

The developers in your organization are building amazing things with AI agents. Our job is to make sure they can keep doing that safely.

Secure Non-Human Identities. Everywhere.

Ofir is the Co-Founder and CEO of Clutch Security. With over 15 years of experience in cybersecurity, including leadership roles at Sygnia and Hunters, he’s helped global enterprises respond to the most advanced cyber threats. At Clutch, Ofir is focused on tackling one of the industry’s most overlooked risks: securing the explosion of Non-Human Identities across modern infrastructure.