Cerbere AG is the runtime security and observability layer for AI agents. Before every tool call runs, it decides whether the action is allowed, needs a human, or is blocked, and it records every decision.

The internet's early years taught us that an open, unguarded system gets exploited. Agentic AI is repeating that lesson, faster.
As homes and offices came online, viruses, worms and bad actors found an unguarded surface. It took firewalls, antivirus and years of hard lessons before connected stopped meaning exposed.
An agent that can read, decide and act can also be hijacked by a poisoned document, a malicious tool response or an injected instruction. Without a layer that checks intent before execution, autonomy becomes risk.
Cerbere AG sits between your agent and its tools. Every call is intercepted, classified, decided on by policy and risk, observed, and written to an audit log. One trace follows it the whole way.
Security means nothing without observability. These are real screens from the dashboard. The SDK and policy engine work standalone too, but this is what you get once a collector is running.
Try the Collector

Each tool call becomes a trace with its arguments, the checks that ran, the decision and the latency. Allowed actions are recorded too, so you can read the whole behaviour of an agent end to end.
Decisions can be cryptographically signed and kept for as long as your plan allows. Filter by agent, tool, verdict or time window when you need to explain what happened.
Atomic token budgets per agent, trajectory tracking and real time alerts on Gmail or Slack when an agent starts behaving outside its normal path.
One policy and telemetry layer across SDKs, providers and agent frameworks.
We ran our detection pipeline against a public benchmark and published the full methodology, strengths and weaknesses, including where it still misses.
recall, 0% false positives
recall
false positives, benign / hard negatives
p95 latency
Agent security research moves fast. Everything that targets your agents today, and where our own benchmark fits into it.
Prompt injection holds the No. 1 spot again, and excessive agency jumped from 6th to 3rd. Our policy chain targets that shift directly: excessive agency is a permissions problem, not just a detection problem.
Tool-integrated agents remain exploitable even under strong system prompts. It's why every call is checked by a layer the agent cannot talk its way around.
Point the SDK at a local collector. Nothing leaves your network. Ideal for prototyping and small teams getting started.
We host the collector and dashboard. Sign up, get an API key, and your agents are covered in minutes with no infrastructure to run.
For high volume or regulated environments: a licensed deployment inside your own infrastructure, with your own data residency and controls.