NVIDIA-NeMo / NVIDIA-NeMo/Guardrails

AgentThreatBench: Benchmark to evaluate guardrail effectiveness against OWASP agentic threats (ASI01/ASI06)

Open
#1,908 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7.2k
Forks
843
Avg merge
3d 1h
Merged PRs (30d)
25

Description

Proposal: Use AgentThreatBench to benchmark NeMo Guardrails effectiveness

AgentThreatBench is an evaluation suite that operationalizes the OWASP Top 10 for Agentic Applications (2026) into executable benchmark tasks. It was recently merged into the official UK AI Safety Institute's inspect_evals repository.

Why this is directly relevant to NeMo Guardrails

NeMo Guardrails is designed to prevent exactly the threats that AgentThreatBench measures:

AgentThreatBench Task Relevant Guardrail Type
Memory Poisoning (ASI06) Input/output rails on memory retrieval
Autonomy Hijack (ASI01) Topical rails on tool output processing
Data Exfiltration (ASI01) Output rails on sensitive data transmission

AgentThreatBench could serve as a standardized test suite for measuring how effectively NeMo Guardrails configurations prevent these attacks — providing a before/after comparison that demonstrates guardrail value.

Example integration
from nemoguardrails import RailsConfig, LLMRails
from inspect_evals.agent_threat_bench import run_benchmark

# Run baseline (no guardrails)
baseline_results = run_benchmark(model="openai/gpt-4o")

# Run with NeMo Guardrails
config = RailsConfig.from_path("./guardrails_config")
rails = LLMRails(config)
guarded_results = run_benchmark(model=rails)

# Compare security scores
print(f"Baseline security score: {baseline_results.security_score}")
print(f"Guarded security score: {guarded_results.security_score}")
Resources

Would love to discuss adding AgentThreatBench to the NeMo Guardrails test suite or documentation as a reference benchmark for agentic security evaluation.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the inspect_evals agent_threat_bench source and benchmark documentation linked in the issue, then inspect the NeMo Guardrails test suite and the RailsConfig/LLMRails entry points. The issue does not choose between a test-suite integration and a documentation reference, so define that scope first; completion should include a reproducible baseline-versus-guarded evaluation for the stated threats.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.