Skip to content

Startup Raises $4M to Police What AI Agents Actually Do at Runtime

Short answer

Kontext, a security startup founded by Jens Ernstberger and Michel Osswald, raised $4 million led by 42CAP with a16z CSX and HTGF to build a runtime platform that evaluates AI agent actions against policy before they execute, addressing risks as agents get file, code and credential access in workplace systems.

What this means for operators

For a 10-200 person B2B company running agents that touch customer records, code repositories or internal tools, the risk isn't the agent's chat output — it's the action it takes once it has credentials. Kontext's pitch is a control point that sits between the agent and your systems, checking identity, requested action and task context before execution, with an observe-only mode to audit behavior first. It's a $4M seed-stage company, so treat it as an early signal rather than a vendor to deploy tomorrow: the category (runtime policy enforcement for agents) is one worth tracking as you scale agent access beyond pilot projects, especially before granting write access to production data or financial systems.

Cybersecurity startup Kontext has raised $4 million to expand a runtime security platform built for AI agents. The round was led by 42CAP, with participation from a16z CSX and HTGF.

Kontext was founded by Jens Ernstberger and Michel Osswald, who bring backgrounds in secure computing, applied cryptography and AI systems. The company's software sits between AI agents and the tools or systems those agents interact with, evaluating each requested action in real time against security policies and risk signals — factoring in the agent's identity, the action requested, the target resource and the assigned task.

The stated problem: an agent can be properly authenticated and using an approved tool, yet still take an action nobody authorized. As agents move from producing text to operating software directly — writing code, accessing files, using company credentials — Kontext argues organizations need a control point at the moment of action, not just at login.

Teams can first run Kontext in observe mode to see how agents behave and how policies would apply without interrupting workflows. Once enforcement is turned on, the platform can block unauthorized actions before execution and keep an auditable record of each decision.

The new funding will go toward expanding the engineering team and continuing development of the runtime enforcement platform to support customers deploying agents with more autonomy.

Source: Tech.eu

Next step

Discovery Sprint

If that argument holds for your operation, the next step is measuring it. Thirty minutes on one process, and we say whether the arithmetic is likely to close.

Put a time in the calendar

Thirty minutes, free. The sprint is what the call is about.

Fee
$2,500
Length
1-2 weeks

Ends in one of two answers: build this, or do not. The process map, the numbers and the ranked backlog are yours either way.