# Probe Overview

Once you start your first probes (test runs), the **Overview** page will begin populating with data. The dashboard provides a **quick view** of your target's metrics, delivering **real-time insights** into recent probe runs and their outcomes.

To view the details of the older Probe Runs, navigate to the [**Test Run History**](/ai-red-teaming/probe/test-run/test-run-history.md). Open one of the older Test Runs which includes the desired Probe and in the [**Probes Table**](/ai-red-teaming/probe/test-run/test-run-view.md#probes-table) click the table row corresponding to that Probe.

<figure><img src="/files/pj3saqosn7bwIfwk8WkH" alt=""><figcaption><p>Figure 1: Overview Page</p></figcaption></figure>

## Overall Score

In the top left corner of the overview, the **Target Overall Score** is displayed. The overall score is a combination of individual category scores, giving you one number that summarizes the performance of your target application. It shows the total number of simulated attacks and successful attacks across different probe categories.  A **higher score** is preferable.

{% hint style="info" %}
The results are taken f**rom the latest available probe runs of each probe**.
{% endhint %}

The Overall Score ranges **0–100**, where **lower numbers mean higher risk**. We group the score into four risk bands:

* 🔴 **CRITICAL:** **< 30**\
  Severe risk. Immediate action required.
* 🟠 **HIGH:** **30–59.9**\
  Elevated risk. Prioritize mitigation.
* 🟡 **MEDIUM:** **60–79.9**\
  Moderate risk. Monitor closely and address issues.
* 🟢 **LOW:** **≥ 80**\
  Low risk. Routine monitoring and improvements.

Toggling the chart switches it to a time series view, allowing you to track your application's overall score over time.

## Category Scores

Similar to the [**Overall Score**](#overall-score), each category score is calculated based on the number of failed test cases, their severity, and their expected probability, taking into account the risk priority set for each probe within that category, which can be customized by the user. **Higher scores** indicate better performance.&#x20;

## Recent Test Runs

The overview of the latest test runs performed on the target is listed here, with the most recent run displayed at the top. Clicking on a test run will open the [**Test Run View**](/ai-red-teaming/probe/test-run/test-run-view.md).

## Categories Overview

In this section, probes are organized by a category, displaying results from their **most recent execution**.  The categories include:

* **Security,**&#x20;
* **Safety,**&#x20;
* **Hallucination & Trustworthiness,** &#x20;
* **Business Alignment,**
* **Custom**.&#x20;

Every **Card** represents a **Probe** from a Category (Figure 1)**.** Each Probe Card provides the probe’s name, the date and time of the last run, and a summary of the results. Clicking on a probe card will open the corresponding [**Probe Run View**](/ai-red-teaming/probe/probe-run/probe-run-view.md).

{% hint style="info" %}

* **Cards** represent **only the most recent Probe Runs**, regardless of the **Test Runs** they belong to
* Each **Probe** result reflects the performance of your target application in that specific area.
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.probe.splx.ai/ai-red-teaming/probe/overview-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.