> For the complete documentation index, see [llms.txt](https://docs.probe.splx.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probe.splx.ai/updates/product-updates/december-2025.md).

# December 2025

## **AI Assets: MCP Servers**

As part of the AI Assets, in addition to Models and AI Workflows, [MCP Servers](/ai-asset-management/mcp-servers.md) have now been added, expanding the ability to scan and manage MCP server infrastructure. The MCP Servers page provides a control panel for monitoring and managing MCP servers from the connected repositories, enabling users to assess server statuses, prioritize issues by severity, and take necessary actions.

<figure><img src="https://1029475228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi12bk7lo75SODuwcRCQp%2Fuploads%2FjFi2j2IIrVRim2zNsDu6%2Fmcp-server.png?alt=media&amp;token=fbf5aaa3-95b8-48bd-90e1-2427b71d2f98" alt=""><figcaption><p>Figure 1: MCP Server Details</p></figcaption></figure>

## **AWS Bedrock Guardrail Policy Generator**

The Policy Generator has been upgraded to now support [the creation of policies for AWS Bedrock Guardrails](/ai-red-teaming/remediation/policy-generator/aws-bedrock-guardrails.md). This improvement allows users to create and manage policies specifically designed to enforce security, compliance, or operational guidelines on AWS Bedrock services with greater ease and efficiency.

## Proxy SDK Connection <a href="#red-teaming-target-new-connection-type-proxy-sdk" id="red-teaming-target-new-connection-type-proxy-sdk"></a>

[Proxy SDK](/ai-red-teaming/probe/target/index/proxy-sdk.md) has been added as a new connection type under the API category for configuring and adding Targets.&#x20;

## **Test For Specific Compliance Policy**

An option is available to [trigger a new Test Run directly from the Compliance Policy page](/ai-red-teaming/probe/compliance.md#test-your-target-against-a-specific-compliance-by-initiating-a-tailored-test-run), with pre-selected Probes mapped to the specific Compliance Policy.

## Multi-step Attacks Toggle  <a href="#add-single-multi-step-attacks-toggle-button-on-target-level" id="add-single-multi-step-attacks-toggle-button-on-target-level"></a>

Users can now toggle the execution of multi-step attacks, enabling support for both conversational targets and those that only accept single-message instructions.

## New Model Benchmarks

Our [Model Benchmarks](/ai-benchmarks/model-benchmarks.md) have been extended to include results for the following models:

* **Anthropic Claude 3.5 Sonnet**
* **Anthropic Claude 3 Haiku**
* **Anthropic Claude Opus 4.5**
* **cohere/command-a**
* **deepseek-ai/DeepSeek-R1-Distill-Llama-70B**
* **Gemini 3 Pro**
* **OpenAI GPT 5.2**
* **xai-org/grok-4.1-fast-reasoning**

## Improvements & Tweaks

* Transition to Zscaler branding.
* Users can now select and assign coverage levels to all probes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.probe.splx.ai/updates/product-updates/december-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
