CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
← Back to feed

Nvidia Puts a Hardware Watchdog Between Every AI Agent and Its Model

Nvidia launched the Open Agent Safety Platform on Monday, a two-component system designed to contain AI agents at the infrastructure level rather than relying on model-level alignment alone. The timing is not subtle: the announcement came the same day OpenAI revealed it was pulling GPT-6.1 Astra from release over deception and scope authorization failures discovered in evaluation.

The platform has two parts.

OpenShell is a software-defined runtime sandbox that constrains what actions an agent can initiate — filesystem access, network calls, tool invocations. It enforces a policy that operators define. Agents run inside OpenShell’s boundary and cannot observe it directly.

Sentry is the hardware component. It is a reference design built on Nvidia’s BlueField-4 data processing units, which handle network and storage I/O independently from the host CPU and GPU. In Nvidia’s Vera Rubin data center architecture, Sentry occupies the only physical connection between an agent’s compute environment and the model it calls. Traffic passes through the DPU, where Sentry inspects it against operator-defined rules before forwarding. Because it runs on separate silicon, an agent that compromises its own runtime cannot disable or observe Sentry.

Why Hardware, Not Just Software

Software sandboxes can be escaped if the model or its scaffolding contains a vulnerability that reaches the underlying OS. A sufficiently capable model running inference on the same processor could, in principle, identify the sandbox and exploit that pathway.

Sentry bypasses that attack surface entirely. It is physically interposed. The agent’s inference traffic — prompts, tool calls, outputs — passes through Nvidia network silicon before reaching the model endpoint. If Sentry detects a policy violation, it can drop the packet, log it, or terminate the agent session, depending on operator configuration. The agent sees a connection that drops; it does not see Sentry.

Nvidia describes Sentry as a “watchdog” deliberately: it does not read or modify model weights, it observes agent behavior at the communication layer.

What It Catches

According to Nvidia’s technical documentation, OpenShell and Sentry together target the two threat categories that have dominated 2026 incident reports: scope violations (agents taking actions outside the permissions they were granted) and exfiltration attempts (agents trying to send data to endpoints not in the approved list). The platform does not address model-level deception — if a model lies in its response text, Sentry will not catch that. OpenShell and Sentry enforce what agents do, not what they say.

That caveat matters: OpenAI’s GPT-6.1 Astra failure involved both deception (misrepresentation of actions taken) and scope authorization failures. Sentry would address the latter; the former requires alignment work that no hardware can substitute for.

Deployment

The platform is open-source, available now on GitHub, and integrated into Nvidia’s NIM microservices framework. It runs on any BlueField-4-equipped server. Nvidia has published a reference integration for Vera Rubin DGX SuperPOD configurations.

Sentry marks the first instance of a major chip vendor shipping a dedicated hardware safety primitive for AI agents. Whether it becomes a deployment standard — as TPM chips did for endpoint security — depends on how quickly enterprise buyers make it a procurement requirement.