Skip to main content

Red Teaming

Find the way in before
somebody else does.

Attack your agent the way an adversary would, in one turn or across a whole conversation, and track a safety score from one release to the next.

Red Teaming in the Netra dashboard

Trusted by teams building and deploying AI agents

What is Red Teaming?

Adversarial testing for your agent, on every release. An attacker model writes attacks from your agent's stated purpose, a judge model scores every reply, and the results roll up into a safety score. You can rerun the same setup on every release and see whether you got safer or not.

An adversary on your release checklist

Save the target, the attack catalogue and the models once, then rerun the same red team on every release.

Save reusable configurations

Keep the agent, evaluators, tests per evaluator and models as a setup, and rerun it every release.

Save reusable configurations: Docs (opens in new tab)

Pick separate attacker and judge models

The attacker writes the prompts and the judge scores the replies. Change one without touching the other.

Pick separate attacker and judge models: Docs (opens in new tab)

Set how many attacks each evaluator runs

Two by default. Raise it for more coverage as a release gets closer.

Set how many attacks each evaluator runs: Docs (opens in new tab)

Attacks written for your agent

Each evaluator's template takes in your agent's stated purpose, so the attacks go after what your agent actually does.

Run single and multi-turn agent attacks

One-shot prompts test individual guardrails. Multi-turn attacks probe escalation and context manipulation.

Run single and multi-turn agent attacks: Docs (opens in new tab)

Test automatically with an autonomous attacker

An attacker agent reads your agent's purpose and keeps probing, with no prompt list to maintain.

Test automatically with an autonomous attacker: Docs (opens in new tab)

Tailor attacks to your agent's purpose

Generation templates use what your agent is for, so a banking agent gets banking attacks.

Tailor attacks to your agent's purpose: Docs (opens in new tab)

Ship with a safety score, not a hope

Every run rolls up into one score, where 100% means every attack was blocked. It breaks down by suite and evaluator to the category that needs work.

See whether a release made you safer

Each run is compared with the one before it, so a regression shows up as a delta on the release that caused it.

See whether a release made you safer: Docs (opens in new tab)

Share reports by suite and evaluator

A breakdown you can hand to engineering, and a history you can hand to compliance.

Share reports by suite and evaluator: Docs (opens in new tab)

Spot the evaluators that fail

The count of evaluators with at least one vulnerable result in the latest run.

Spot the evaluators that fail: Docs (opens in new tab)

Evidence for engineering and for compliance

Every attack, response, judge score and explanation is kept, multi-turn transcripts included.

Read detailed results

Pass, fail or error for every attack, with the judge's score and its explanation.

Read detailed results: Docs (opens in new tab)

Replay multi-turn transcripts

See the whole exchange, turn by turn, and where the agent gave way.

Replay multi-turn transcripts: Docs (opens in new tab)

Trace every attack

Runs emit telemetry, so a successful attack opens in the same trace view you use for production.

Trace every attack: Docs (opens in new tab)

Open source

Red teaming you can read the source of

Open source · Apache 2.0

Agent OPFOR — adversary emulation for AI agents

The adversarial framework we red team agents with, open source on GitHub. Run it yourself, read how every attack is generated, and contribute new ones.

View on GitHub (opens in new tab)

How a run works

  1. 01Point it at an agent registered in your project
  2. 02Pick suites aligned to security frameworks, or single evaluators
  3. 03An attacker LLM generates prompts tailored to your agent's purpose
  4. 04A judge LLM scores every response, single- or multi-turn
  5. 05Results roll up into a safety score you can track release to release
Frequently Asked Questions

Everything You Need to Know About Red Teaming

Can't find the answer here? The Red Teaming docs go deeper, or talk to our team.

How does automated AI agent red teaming work?

Automated AI agent red teaming uses an attacker model to generate adversarial inputs and test them against a target AI agent. A judge model evaluates the agent's responses to determine whether the attacks succeeded or failed. Netra automates this process through predefined evaluation suites, purpose-specific attack generation, and single-turn or multi-turn tests. Results are recorded with safety scores and detailed evaluation reports.

How is AI agent red teaming different from regular evaluation?

AI agent evaluation measures how well an agent performs against defined criteria such as response quality, task completion, or accuracy. Red teaming specifically tests how the agent behaves under adversarial conditions, such as prompt injection, jailbreaks, and attempts to bypass security guardrails. Netra supports both evaluation and red teaming, helping teams assess agent performance and security throughout development and production.

What security vulnerabilities can Netra's AI agent red teaming detect?

Netra tests AI agents against adversarial attacks such as prompt injection, jailbreaks, system prompt leakage, policy bypass, and excessive agency. Tests can be run using predefined evaluation suites aligned with security frameworks or individual evaluators targeting specific vulnerabilities.

What is the difference between single-turn and multi-turn red teaming?

Single-turn red teaming tests an AI agent with individual adversarial inputs to identify immediate vulnerabilities. Multi-turn red teaming tests the agent across a sequence of interactions to identify vulnerabilities that emerge through context manipulation, escalation, or repeated attempts to bypass guardrails. Netra supports both approaches to test agent security across different attack scenarios.

How does Netra calculate an AI agent's safety score?

Netra evaluates an agent's responses to adversarial attacks using a judge model. Each test receives an evaluation result, which contributes to the overall safety score. A score of 100% indicates that all evaluated attacks were blocked in that test run. Results can also be reviewed by security evaluation suite and individual evaluator to identify areas that need improvement.

What do I need before my first run?

An agent registered in your project, an attacker model and a judge model configured, and at least one suite or evaluator selected.

Is the attack framework open source?

Yes. Agent OPFOR, the adversarial framework we red team agents with, is on GitHub under Apache 2.0.

How do I know whether a release made things worse?

Score change is always computed against the immediately previous completed run, and every run is plotted on the score history — so a drop is visible on the release that caused it.

Can I run AI agent red teaming on every release?

Yes. Netra lets you save your red team configurations and reuse them across releases. You can run the same security evaluations, compare safety scores, and identify regressions introduced by changes to your AI agent. This helps teams make security testing a repeatable part of their development and release process.

Start today

Find the way in on your own terms

Point a red-team run at your agent and get a safety score before your next release. Free to start.