Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Run Scan

Running security probes in Akto involves assessing agent components to evaluate their security posture. You can run probes instantly or schedule them for later, making it useful for planning probing sessions or implementing regular security validation.

Running Probes on Agent Components

1

Navigate to Agentic AI Discovery > Collections

2

Select the collection containing the agent components you want to probe

3

Choose specific agent components or select all components in the collection

4

Click Run Scan to open the Configure scan window

5

(Optional) Edit the Name field to identify this scan run.

Akto auto-generates a name based on the target and selected tests, but you can rename it or click Clear selection to reset the test selection.

6

Select Test Categories and Tests to run.

The window shows two panels:

  • Test Categories (left): broad groupings such as Model Context Protocol (MCP) Security, MCP - Broken Authentication, MCP - Denial of Service, MCP - Indirect Prompt Injection, MCP - Input Validation, and MCP - Malicious Code Execution. Each category shows how many tests within it are selected (e.g., 43 out of 43 selected).

  • Tests (right): the individual tests inside the selected categories, each with its own checkbox. Tests you or your org have created show a Custom tag. Use the checkbox at the top to select/deselect all, or use More filters and the search icon to narrow the list.

Estimated Usage at the bottom of the panel shows the projected token consumption for the current selection, updating live as you add or remove tests. Use this to evaluate expected LLM consumption before starting the scan.

7

Configure the scan execution parameters.

Scan Execution Parameters
Parameter
Description

Run Type

Defines how the scan runs. You can run the scan once or configure scheduled execution.

Select Date

Defines the date when the scan execution starts.

Select Time

Defines the time when the scan execution begins.

Scan Run Time

Defines the maximum duration allowed for the scan execution. The scan stops automatically when the configured duration expires.

Select Scan Role

Associates a predefined scan role that defines permissions and execution behavior for the scan.

Max Concurrent Requests

Controls the number of parallel probe requests executed during the scan. Higher concurrency increases scan speed but also increases request load.

Max Agent Tokens

Defines the maximum number of tokens that the agent can consume during the scan. The No limit option allows unrestricted token usage.

Select Testing Module(s)

Chooses which probing module(s) execute the scan. See Scanning Module Selector in Akto.

8

(Optional) Turn on post-scan actions:

  • Send slack alert post test completion: sends a notification to the selected Slack Channel once the scan finishes.

  • Send MS Teams alert post test completion: sends a Microsoft Teams notification once the scan finishes.

  • Auto-create tickets: automatically opens tickets for issues found by the scan.

  • Use different target for scanning: lets you point this scan at a target other than the one associated with the collection.

  • Mark issues as fixed if they don't show up again: automatically closes previously reported issues that no longer reproduce in this scan run.

  • Smart Automated Testing: lets Akto adapt test execution automatically instead of running the fixed selection as-is.

9

(Optional) Click Show advance configurations to add custom headers or conditions to the scan's requests.

  • Choose Add Header, enter a key/value pair, and use Add condition to chain multiple headers with AND/OR logic.

This is useful for authentication tokens or agent-specific request requirements.

10

Click Run once now (the button label follows the selected Run Type, e.g. Schedule scan for scheduled runs) to start the security scan.

PreviousHow To
NextRun Bulk Scanning

Last updated