Before you start
- A voice, chat, or SMS agent in Bluejay. Red Teaming does not support email agents. See Connect your agent.
- For Custom intensity, the Growth, Scale, or Enterprise plan.
Steps
1
Launch a red team
Open Red Teaming and click Launch red team. Choose the target agent, then an Intensity.



- Use Quick for a smoke test while you iterate, and Thorough for the run you share, because it escalates deepest.
- Custom sets the number of attempts for each attack family, and a family set to 0 is skipped. Launch stays disabled until at least one family is above 0.
2
Give the attacker partial account details
To test your verification steps, open the Attacker knowledge tab and add what a real attacker might already know about the customer, for example a date of birth or the last four digits of a card. Only the social engineering callers use it.

If the attackers dial into an inbound agent that needs an extension, enter it on the Connection tab.


3
Start the run and wait for it to finish
Click Launch red team. The callers first learn what data and tools your agent has, then push harder with the tactics that work. The run ends when it reaches its call limit, or when you stop it.



4
Read the verdict for each category
On the Report tab, start with the verdict and the categories listed under Breached. Then check Conceded ground, where the agent resisted but gave up some ground. Categories under Not assessed did not run, so a higher intensity is the way to cover them. See Read the results for what each verdict means.

Content-harm categories are in the same report. A content-harm failure alone fails the run. See OWASP coverage and content harm.


5
Open each breach
On the Swarm tab, click an attacker marked Breached, then open Transcript to read the conversation that breached the agent. Read the words that worked and find the gate that was missing or bypassed.



6
Fix each breach
Pick the fix that matches the gap:
- The agent said something it should not have: tighten its prompt.
- The agent acted without checking who was calling: add or tighten the verification step.
- The agent took an action the caller should not reach: remove tool access the agent does not need.
7
Run the same intensity again
Launch again with the same intensity and attacker knowledge, so the two reports are comparable. Changing either one makes a better score hard to trust.


