How Dome Works
Dome sits in the Agent’s request path and checks traffic in both directions: Input Guards check user requests before they reach your Agent. Use them to block prompt injection, jailbreak attempts, harmful requests, or sensitive data you want to keep out of downstream systems. Output Guards check Agent responses before they reach users. Use them to reduce data leakage, unsafe content, or responses that violate your policies.Open Dome Settings
Configure Dome from the Agent you want to protect:- Open Agents in the Console sidebar.
- Select the Agent you want to protect.
- In the Actions row, click Protect.
- Configure the Agent’s Input Guards and Output Guards in the Dome settings view.
Configure Guards
The Dome settings view has separate sections for Input Guards and Output Guards. Dome starts each Agent with predefined Guards:
Configure each side based on what you want Dome to check before and after the Agent runs.
- Review the predefined Guards and use each Guard toggle to enable or disable it.
- Click the + symbol next to a Guard name to add a Detector, then choose from the dropdown.
- Click + Add Guard only when you need another Guard beyond the predefined set.
- If a predefined Guard is still missing, Dome adds that predefined Guard first: Privacy Input Guard for input, or Security Output Guard for output.
- After the predefined Guards exist, + Add Guard creates a new custom Guard such as
new-input-guard-#ornew-output-guard-#. - Set Serial or Parallel execution.
- Set Early Exit based on whether Dome should stop at the first triggered Guard.
- Click Save, then Apply when you are ready to activate the configuration for the Agent.
Choose Guard Types
Dome shows three Guard types in the Console for Agent owners: Security, Moderation, and Privacy. Each Guard type covers a different class of runtime risk.Security Guards
Security Guards detect adversarial content that tries to manipulate the Agent or bypass its intended instructions. Use Security Guards for:
Dome enables
security-guard by default in Input Guards with encoding-heuristics and prompt-injection-mbert. If you add a missing Security Guard to Output Guards, the Console exposes encoding-heuristics, prompt-injection-mbert, security-llm, and security-embeddings.
Enable Security Guards first for customer-facing Agents, Agents with tool access, and Agents exposed to unknown users.
Moderation Guards
Moderation Guards detect harmful or policy-violating content in user requests, Agent responses, or both. Use Moderation Guards for:
Dome enables
moderation-guard by default in both Input Guards and Output Guards with moderation-flashtext and moderation-mbert.
The Console exposes moderation-flashtext, moderation-mbert, moderation-prompt-engineering, and moderation-deberta.
Enable Moderation Guards on inputs to block harmful requests, and on outputs to prevent the Agent from returning harmful content.
Privacy Guards
Privacy Guards detect sensitive data that should not reach the Agent or leave the Agent response. Use Privacy Guards for:
Dome enables
privacy-guard by default in Output Guards with privacy-presidio. If you click + Add Guard in Input Guards while the predefined Privacy Input Guard is missing, Dome adds that predefined Guard before creating a custom Guard.
The Console exposes privacy-presidio and detect-secrets Detectors.
Enable Privacy Guards on outputs to reduce sensitive-data leakage. Add Privacy Guards on inputs when users may send data you do not want the Agent or downstream tools to process.
Execution Settings
Execution settings control how Dome runs Guards and Detectors.Serial and Parallel
Use Serial when order matters or when you want the clearest execution trace. Use Parallel when Guards are independent and you want lower latency. Input and output sections can have their own execution mode. Individual Guards may also expose execution settings for their Detectors.Early Exit
With Early Exit on, Dome stops processing after the first Guard or Detector triggers.- Enable it when a triggered Guard is enough to block or transform the request.
- Disable it when you want fuller detection coverage for investigation, tuning, or reporting.
Test the Configuration
Before applying changes, use the test panel in the Dome settings view to check how content flows through the configured Guards.- Expand Test Input Guards when validating input protection.
- Enter a representative prompt or attack sample.
- Run the test.
- Review which Guards triggered and whether the result matches your policy.
- Repeat with output-focused examples when tuning Output Guards.
Review Operational Context
The Dome settings view also shows operational context for the selected Agent:
Use this context to decide whether the configuration is broad enough, fast enough, and ready to apply.
Save, Apply, and Export
Use the top-level controls to manage the Agent’s Dome configuration:
After you configure and enable Dome, the Agent can move to the Protected stage.
Best Practices
- Start with the highest-risk path: Use Security input Guards first for customer-facing Agents and Agents with tools or sensitive data.
- Map Guards to evidence: Use evaluation failures, Red Team findings, and policy requirements to justify each Guard.
- Keep latency visible: Use Parallel execution only when Guards are independent, then watch P99 latency after applying changes.
- Test before applying: Use known attack, privacy, and moderation examples before activating the configuration.
- Track after applying: Review Observability for false positives, missed detections, and latency changes.
Next Steps
Deploy Dome
Hand off runtime integration work
Observe Traces
Track Guardrail performance
Developer Configuration
Configure Dome in code
Detection Methods
Review available Detectors