diff --git a/docs/developer-tools/snyk-cli/commands/aibom-test.md b/docs/developer-tools/snyk-cli/commands/aibom-test.md
new file mode 100644
index 000000000000..844d93bbcf5f
--- /dev/null
+++ b/docs/developer-tools/snyk-cli/commands/aibom-test.md
@@ -0,0 +1,81 @@
+# AI-BOM test
+
+**Note**: AI-BOM is an experimental feature and is subject to breaking changes without notice. If you are using AI-BOM, Snyk recommends installing the Snyk CLI from the [release](../releases-and-channels-for-the-snyk-cli.md#stable) channel.
+
+## Prerequisites
+
+- The `snyk aibom test` feature requires an internet connection.
+- Snyk CLI v1.1304.0 (or later).
+- Your Snyk Organization must have Evo policies configured (for example, in the Evo web interface).
+
+## Usage
+
+`$ snyk aibom test --experimental [<OPTION>]`
+
+## Description
+
+The `snyk aibom test` command generates an AI-BOM for your local project and evaluates it against your tenant's Evo policies. It reports all policy violations as issues, so you can see which AI models, tools, or other components are disallowed or non-compliant.
+
+The command:
+
+1. **Generates an AI-BOM** for the current project (same behavior as [`snyk aibom`](aibom.md)), detecting AI models, agents, tools, and MCP dependencies.
+2. **Runs a policy test** against the policies configured for your Organization.
+3. **Returns all resulting issues**, grouped into **Open issues** (active policy violations) and **Ignored issues** (violations that are configured to be ignored).
+
+For each issue, the output includes:
+
+- **Severity** (LOW, MEDIUM, HIGH, CRITICAL)
+- **Description** of the policy violation (for example, a disallowed model or asset)
+- **Policy link** to view or edit the policy in the Evo web interface
+- **Remediation advice** when the policy provides it
+
+A **Test summary** at the end shows the total count of open and ignored issues by severity.
+
+## Exit codes
+
+Possible exit codes and their meaning:
+
+**0**: success (scan completed), no open policy issues.\
+**1**: action_needed (scan completed), one or more open policy issues found.\
+**2**: failure, try to re-run the command. Use `-d` to output the debug logs.\
+**3**: failure, unable to find any supported files for the scan.
+
+## Debug
+
+Use the `-d` or `--debug` option to output the debug logs.
+
+## Options
+
+### `--experimental`
+
+**Required**. Use experimental command features. This option is required because the command is in its experimental phase.
+
+### `--org=<ORG_ID>`
+
+Specify the `<ORG_ID>` to run the policy test against the policies of a specific Snyk Organization.
+
+If you have multiple Organizations, you can set a default from the CLI using:
+
+`$ snyk config set org=<ORG_ID>`
+
+Set a default to ensure all newly tested Projects are tested under your default Organization. If you need to override the default, use the `--org=<ORG_ID>` option.
+
+Default: `<ORG_ID>` that is the current preferred Organization in your [Account settings](https://app.snyk.io/account)
+
+## Example
+
+```bash
+snyk aibom test --experimental
+```
+
+This generates an AI-BOM for the current directory, runs the policy test for the current preferred Organization, and prints open issues, ignored issues, and the test summary.
+
+### `--json-file-output=<OUTPUT_FILE_PATH>`
+
+**Optional.** Write the policy test results to a JSON file at the given path instead of printing the report. The JSON includes full issue details and closed issues, which are not shown in the on-screen report.
+
+Example: `$ snyk aibom test --experimental --json-file-output=results.json`
+
+### `--severity-threshold=<low|medium|high|critical>`
+
+**Optional.** Minimum severity that triggers `action_needed` (exit code 1). Only issues at or above this level cause the command to exit with 1. Default: `low`.
diff --git a/docs/developer-tools/snyk-cli/commands/aibom.md b/docs/developer-tools/snyk-cli/commands/aibom.md
index d9147d86c39a..3ae5a825d53e 100644
--- a/docs/developer-tools/snyk-cli/commands/aibom.md
+++ b/docs/developer-tools/snyk-cli/commands/aibom.md
@@ -4,14 +4,15 @@
 
 ## Prerequisites
 
-* The `snyk aibom` feature requires an internet connection.
-* Snyk CLI v1.1298.3 (or later).
-* Your Project must be written in Python and using a [package manager](../../../supported-languages/supported-languages-list/python/) supported by Snyk.
+- The `snyk aibom` feature requires an internet connection.
+- Snyk CLI v1.1298.3 (or later).
 
 ## Usage
 
 `$ snyk aibom --experimental [<OPTION>]`
 
+**See also:** [`snyk aibom test`](aibom-test.md) — generate an AI-BOM and test it against your tenant's policies.
+
 ## Description
 
 The `snyk aibom` command generates an AI-BOM for a local software Project that is written in Python. You can use the `snyk aibom` command to identify AI models, datasets, and map the AI supply chain, including connections to external tools and services using the Model Context Protocol (MCP).
@@ -20,10 +21,10 @@ The supported format is CycloneDX v1.6 (JSON).
 
 In the JSON file, you can see the following AI dependencies and components:
 
-* **Models:** You can see your usage of foundational models (such as GPT-4) and open-source models (such as Llama-4). Where possible, the information surfaced also refers to model card, license, and other information.
-* **Agents:** Identified based on popular AI agent libraries.
-* **Tools:** Identified based on popular patterns of tool calling.
-* **MCPs:** Identified based on the official MCP SDK, in addition to other popular ways of building MCPs.
+- **Models:** You can see your usage of foundational models (such as GPT-4) and open-source models (such as Llama-4). Where possible, the information surfaced also refers to model card, license, and other information.
+- **Agents:** Identified based on popular AI agent libraries.
+- **Tools:** Identified based on popular patterns of tool calling.
+- **MCPs:** Identified based on the official MCP SDK, in addition to other popular ways of building MCPs.
 
 ## Exit codes
 
@@ -45,14 +46,12 @@ MCP is an open standard that applications use to connect LLMs with external tool
 
 `snyk aibom` analyzes your source code to identify and categorize MCP components into a clear dependency graph:
 
-* **MCP client**: The component in your code that initiates a connection to a server.
-* **MCP server**: The component providing tools or resources. This can be a local script or a remote network service.
-* **Tools and resources**: The specific functions (tool) or data (resource) made available by an MCP server.
+- **MCP client**: The component in your code that initiates a connection to a server.
+- **MCP server**: The component providing tools or resources. This can be a local script or a remote network service.
+- **Tools and resources**: The specific functions (tool) or data (resource) made available by an MCP server.
 
 When you run `snyk aibom`, the output shows these dependencies clearly. For example, you can see a chain showing that your root application depends on an mcp-client, which depends on an mcp-server, which in turn provides a specific tool. This gives you full visibility into the services your AI application relies on.
 
-**Note:** AI-BOM scans are included for Snyk users using the Snyk CLI.
-
 ## Options
 
 ### `--experimental`
@@ -79,13 +78,13 @@ Default: `<ORG_ID>` that is the current preferred Organization in your [Account
 
 **Optional.** Save the AIBOM output as a JSON data structure directly to the specified file.
 
-#### Upcoming Features in 1.1303.0
+#### Available in 1.1303.0
 
-### `--upload`
+### `--upload`&#x20;
 
 **Optional**. Persist the AIBOM into your Snyk Organization. This flag requires the [`--repo`](aibom.md#repo) flag. It enables you to view your AI-BOM for the repository in the Evo web interface.
 
-### `--repo`
+### `--repo`&#x20;
 
 **Optional**. Specify the repository to use when persisting the AI-BOM. Required when you use the [`--upload`](aibom.md#upload) flag.