Reco Raises $55M to Secure the AI Agents Enterprises Cannot See

AI agent adoption is moving faster than enterprise visibility. Reco, a security startup focused on mapping software and AI environments, said Tuesday that it raised $55 million in new funding as companies struggle to discover what their agents can access.

What happened

The extension round includes AT&T Ventures, Forestay, and Quadrille Capital, building on Reco’s $30 million Series B announced in February. The new financing brings the company’s total capital raised to $140 million, according to TechCrunch, which reported the news on September 29.

Reco is repositioning its platform around a context graph that connects agents to applications, people, accounts, and permissions. CEO Ofer Klein told TechCrunch that the platform found 21,000 previously unknown agents at one Fortune 100 customer. At a financial-services customer, it reportedly identified an agent created by a former employee that could reach Salesforce and share data with an unseen domain.

The company says it integrates with more than 280 applications and can inspect prompts and tool calls. Reco plans to use the funding for hiring, sales, partnerships, and customer support.

Why it matters for builders

The important signal is not the size of the round. It is the shape of the problem: an AI agent is becoming an identity with permissions, integrations, and a runtime, not just a model endpoint.

For teams building agents and automations, that means the security checklist has to move beyond API-key storage. Builders need an inventory of active agents, explicit access boundaries, logs for tool calls, and a fast way to revoke privileges when an agent behaves unexpectedly. In an n8n workflow, the same principle applies to every credential, sub-workflow, webhook, and external action connected to an AI node.

Reco’s funding also shows that agent security is becoming its own infrastructure category. The market is crowded, but the practical demand is clear: enterprises want to adopt agents without creating an invisible second network of software identities.

Builder takeaway: Treat every production agent as a service account with a blast radius. Discover it, scope it, observe it, and make shutdown a tested workflow rather than an emergency procedure.