Context Receives 3.5 Million Euros to Monitor AI Agents | Startbase
Context Receives 3.5 Million Euros to Monitor AI Agents | Startbase
摘要: Javascript is disabled in your browser
Startbase requires Javascript in order to display content.
Please check your browser settings and enable Java
正文
Javascript is disabled in your browser
Startbase requires Javascript in order to display content.
Please check your browser settings and enable Javascript-Support for this website.
Your browser is outdated and Startbase will not be displayed correctly.
Please use a modern web-browser like
Mozilla Firefox
Google Chrome
Microsoft Edge
.
Startbase.com
Magazine
Context Receives 3.5 Million Euros to Monitor...
Cybersecurity
Context Receives 3.5 Million Euros to Monitor AI Agents
42CAP is leading the funding round for the Munich-based startup. a16z CSX and HTGF are also investing in the security platform for AI agents.
Marc Nemitz
München, 24. September 2026
Kontext Gründer
The Munich-based cybersecurity startup Kontext has raised 3.5 million euros, or 4 million U.S. dollars. The funding round is led by 42CAP, with additional participation from a16z CSX and the High-Tech Gründerfonds (
). The company, founded by Jens Ernstberger and Michel Osswald, plans to use the capital to expand its development team and further develop its security platform for autonomous AI agents.
Security checks immediately before an action
Kontext addresses a security issue arising from the increasing autonomy of AI agents. While traditional identity and access management systems primarily control who is allowed to access a system, Kontext aims to additionally verify what an AI agent is actually permitted to do within that system.
To achieve this, the software positions itself between an AI agent and the tools or systems it accesses. Every planned action is checked in real time against security policies and risk signals.
In doing so, Kontext takes into account not only an agent’s identity and access rights, but also its specific task, the requested action, and the affected resource.
Valid credentials are not enough
This distinction becomes relevant as soon as AI agents operate with more extensive permissions.
For example, an agent