Agent reports

Agent reports perform automated black-box adversarial testing against a deployed AI agent. They discover capabilities, exercise relevant attack hypotheses, preserve evidence, and report verified security-boundary failures without requiring source-code access.

Create an agent report

Open Red team and select New report, or go to /app/reports/new.
Choose Agent.
Select an agent type (chatbot, voice agent, coding agent, AI workflow, data pipeline, or other).
Choose the target type: Web app or API.
Enter the public target URL, configure optional encrypted headers, and add a specific prompt when needed.
Submit to provision the isolated runner and open the live detail page.

The report name defaults to the target host. Agent reports created in the dashboard are labeled Manual in the report list. Reports created through REST or MCP are labeled API.

Web app targets

Use Web app when the AI agent is accessed through a browser interface. Superagent generates test credentials that you can view, edit, or copy before starting the report. You can also add encrypted headers for staging gates, tenant selection, or authentication.

The isolated runner interacts only with the configured origin. Browser interaction evidence can appear in the Evidence tab when recording is available.

API targets

Use API when the AI agent is exposed through an HTTP or WebSocket endpoint. Enter only the endpoint URL. Add authentication or tenant headers under Headers.

Describe the API contract in Specific prompt, including:

HTTP method and example JSON payload
Where the attack prompt belongs
Required model or deployment identifier
Expected response or streaming shape

For example:

POST JSON like:
{
  "model": "qwen/qwen3.7-flash",
  "stream": false,
  "messages": [
    { "role": "system", "content": "You are a helpful assistant." },
    { "role": "user", "content": "<attack prompt>" }
  ]
}

API reports expose Logs and Findings. They do not show browser evidence.

REST API and MCP

Programmatic clients can create either modality with:

POST /api/v1/reports/agent
MCP tool create_agent_report

Both accept target_type as web_app or api. See the Reports API for request fields and examples.

The agent detail page

Each automated Agent report lives at /app/reports/agent/[id]. From there you can:

Follow expandable runner logs
Review findings and risk counts
Inspect target, assignees, cost, and runtime status
Delete or rerun the report
Review browser evidence for Web app targets

Best practices