- Content Guards intercept every input and output and block flagged content. This is the Guardrail → Guard → Detector model described below.
- The Trust Runtime secures the Agent as an actor: it attests the Agent’s identity, enforces which tools the Agent may call, and emits an audit trail. A single
secure_agent()call applies both content Guards and tool-permission enforcement.
- simple pattern matching
- machine learning classifiers
- embedding-based similarity checks
- and LLM-based evaluation
Defense Components
Under the hood, Dome follows a clear hierarchy for how content protection is applied. A Guardrail contains one or more Guards, and each Guard runs one or more Detectors. You do not need to configure everything from scratch, but understanding this hierarchy makes it easier to see how decisions are made and where controls are applied.Guardrail
Defines what kind of behavior you want to control, such as blocking sensitive data, preventing prompt injection, or enforcing content policies.
Guard
The building blocks inside a Guardrail. Each Guard focuses on a specific category, such as scanning for secrets, toxic language, or unusual patterns.
Detector
The engines that evaluate the data. Detectors analyze inputs and outputs and decide whether something should be flagged, blocked, or modified.