Skip to main content
Red Team attacks a registered Agent to find weaknesses a fixed Harness would miss. It creates an Engagement that runs in waves: each wave generates attack seeds from a risk taxonomy, pursues them over multiple turns, judges the transcripts, and reflects on what worked before planning the next wave. For the mechanics, see Engagements. This page covers reaching Red Team from outside the Console.

Interfaces

Create an Engagement

Only the Agent ID is required. The service resolves the target endpoint and Agent card from the Agent registry, so you never pass an endpoint directly.
Both override blocks are optional:
The exact override keys come from the vijil-redteam schemas package rather than from the Console, so run vijil redteam create --help to see the set your deployment accepts.

Follow a Run

An Engagement reports status, phase, current_wave, attackers_completed, and attackers_errored while it runs.
A completed Engagement can report degraded with a degradation_reason when the target failed mid-run, which means the report is partial rather than a clean pass.

Read the Results

Findings are addressable per wave and per seed, so you can pull one transcript rather than the whole run. Every endpoint takes team_id as a query parameter.

Personas and Policies

Personas and Policies are the context an Engagement attacks with and judges against. An Engagement given neither still runs, but its judgments fall back on general safety and security expectations rather than your rules. Create both from presets:

Next Steps

How Engagements Work

Waves, seeds, judgments, and reflections

CLI Reference

Every Persona, Policy, and Engagement command

MCP Tools

The Red Team tool catalog for Agents

Run From the Console

Launch Red Team from the UI
Last modified on September 24, 2026