Server and Python SDK 3.2.3

DeepIntShield Server 3.2.3 and Python SDK 3.2.3 - 23 October 2026.

This is a correction release on 3.2.2. It changes one SDK behaviour, the automatic governance of AWS Strands Agents 1.62, and aligns the gateway, chart, package and documentation reference at 3.2.3; the gateway’s APIs, configuration and data are unchanged, and every 3.2.2 client keeps working. Check the version and enabled capabilities of your own gateway: a documentation release does not establish what is deployed.

AWS Strands 1.62 is governed again

Strands 1.62.0 moved its middleware stages from the private strands._middleware package to the public strands.middleware package, and its tool-execution terminal gained three telemetry options (tracer, cycle_span, cycle_trace) because Strands now opens the tool span inside that terminal. SDK 3.2.2 recognised only the earlier terminal shapes. Because an imported framework that cannot be guarded fails closed, with Strands 1.62 installed every DeepintShield(...) created after import strands, and any import strands after a client existed, raised:

governance_configuration_error: Agent governance is not fully configured. Please contact your administrator.

SDK 3.2.3 guards the 1.62 terminal the way it guards Strands 1.55.1 to 1.61.1:

• Authorization runs on the final tool and arguments, after any middleware or hook has selected them, and before Strands opens the tool span. A denied or approval-pending call never executes and opens no span; an approved call then runs, and Strands records its span and metrics as usual.
• The telemetry options are passed through unchanged, as are the background-tool context, the native tool guard and a preset rejection, which is still returned without an authorization decision.
• Strands 1.55.0 to 1.61.1 behave exactly as with 3.2.2, and a terminal shape the SDK does not know still fails closed.

Applications that cannot upgrade yet keep 3.2.2 working by pinning strands-agents<1.62.

Server 3.2.3

Server, UI, MCP handshake, Helm chart and npm package metadata are aligned with SDK 3.2.3. There is no API, configuration or schema change, and no migration. Container and npm publication are separate release steps.

Upgrade

python -m pip install --upgrade "deepintshield==3.2.3"
# with the Strands integration:
python -m pip install --upgrade "deepintshield[strands]==3.2.3"

No configuration change, no new variable and no migration are required. For the 3.2.2 changes (decision targets validated before authorization, an over-limit blueprint scan reported as incomplete coverage, guardrail evaluation naming the policies it evaluated, streaming errors keeping their status and message, the composite LangGraph node at first execution), see Server and Python SDK 3.2.2.