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.- CLI
- MCP
- REST API
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 reportsstatus, phase, current_wave, attackers_completed, and attackers_errored while it runs.
- CLI
- MCP
- REST API
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