What you are evaluating
This profile covers the NeMo Guardrails library, not an automatically managed enterprise security service. Supported models, rail engines and deployment options differ; an enabled input rail does not imply that retrieval or tool execution is also protected.
A useful evaluation context
Developers who can operate their own middleware can examine programmable controls and their integration responsibilities.
Documented capabilities
The vendor describes these capabilities in the linked sources. Availability depends on the product edition and supported environment.
- Input and output rails can validate, transform or reject content at the corresponding boundaries.
- Retrieval and dialog rails address retrieved context and conversation flow separately.
- Execution rails validate tool or function interactions; application permissions remain a separate boundary.
Where it fits in the work
- Pin the library and model versions and draw the application call sequence.
- Enable one explicit rail and record which event invokes it.
- Test the same case through retrieval, direct tool and streaming paths to discover where additional controls are needed.
APPLY THE IDEA / ILLUSTRATIVE EXERCISE
Make the outcome observable.
Build a synthetic document assistant with a mock tool and compare input filtering with an execution check.
Evidence to look for
The trace demonstrates which rail ran and whether the mock tool was called; a blocked answer alone is not counted as a blocked action.
Use synthetic data and an authorized test environment. Agree the scope and recovery steps before enabling enforcement.
Questions for your evaluation
- Which rail engine supports the desired control and model?
- Can any application path call the model or tool outside the configured rails?
- What telemetry is captured, and does it include unnecessary sensitive content?