Quarantine is a GTM control

When a GTM agent breaks a rule, pause it. Do not schedule a retrospective while it keeps sending.

On Sep 28, TechCrunch's Kirsten Korosec reported that Nvidia launched an Open Agent Safety Platform pairing OpenShell with BlueField-4 Sentry to quarantine breakout agents. Anthropic, Microsoft, Oracle, and SpaceX were listed among the names in that coverage. Jensen Huang said the approach would have blocked recent lab escapes. Steal the pattern for GTM ops. When an agent burns domain, spoofs tone, or writes junk into CRM, quarantine beats "we will review later."

Quarantine on rule break. Review after, not instead.

How is quarantine different from a kill switch?

A kill switch stops outbound. Quarantine isolates the actor and its tools.

I already wrote about the kill switch for outbound. That control is about send volume and domain risk. Quarantine is wider. It pauses send, revokes tool scopes, and freezes write-back for that agent or workspace until a human clears it. The kill switch can be global. Quarantine is usually targeted: this agent, this Clay table, this MCP server, this inbox seat.

Nvidia's hardware watchdog is proof that serious systems assume breakout is possible. Your SaaS stack will not get a BlueField card. You still need a named quarantine state in ops.

What should trigger quarantine in GTM?

Write the triggers before the incident. Three buckets cover most pain.

1. Buyer-facing damage. Bounce spikes, spam complaints, tone that fails a side-by-side with your approved voice, replies that invent pricing.
2. System damage. CRM writes that fail validation, duplicate accounts created in bulk, enrichment that overwrites owner or stage, secrets pasted into a prompt log.
3. Scope damage. An agent calling tools it was never granted, an unofficial MCP server appearing on a prod path, a personal automation using a shared API key.

When a trigger fires, the agent moves to quarantine automatically. Humans review inside the fence. They do not debate while the fence is open. That is the same discipline as CRM write-back rules: state changes need constraints, not vibes.

What does quarantine look like in practice?

Four moves, in order, under five minutes.

1. Pause send for that agent and any sequence it owns. If you only have a global kill switch, use it, then narrow later.
2. Revoke tools. Cut CRM write, inbox send, and paid enrichment keys. Leave read-only if you need forensics.
3. Freeze write-back. Queue or drop pending CRM updates from that agent so bad data stops spreading.
4. Open a ticket with the trigger, last 50 actions, and owner. Review happens here. Clearance is explicit: restore tools one at a time, not "turn it all back on."

This pairs with the send wall. The wall is the gate before production send. Quarantine is what happens when something that already had access breaks a rule.

Why do teams stall on quarantine?

Because quarantine feels like admitting the agent failed, and vendors sell "always on."

Always on without a fence is how you get a week of quiet damage and a loud apology. Buy the agent, build the rails includes the off ramp. If your runbook says "escalate to Slack and discuss," you do not have a control. You have a group chat.

Convert cares because quarantine protects the path buyers actually feel: inbox, calendar, CRM truth the AE reads before the call. A poisoned convert path loses meetings even when Signals were right.

What should I do Monday?

Name three quarantine triggers in a one-pager. Wire one automatic pause on send for the loudest trigger you can measure this week (bounce spike or validation fail on CRM write). Rehearse the revoke steps on a non-prod agent. Put the runbook where the on-call GTM eng will actually find it at 11 p.m.

Adapt or fail. Review without quarantine is a postmortem with an open blast radius.

Start Signals, Convert, Grow

FAQ

Is quarantine the same as turning the vendor off?

No. Quarantine isolates one agent or workspace. You may keep other agents live. Vendor-off is the nuclear option when you cannot trust the integration boundary.

Who can clear quarantine?

One named role, usually GTM engineering with a security or RevOps check for data incidents. "Anyone in the Slack channel" is how quarantine becomes optional.

What if leadership wants send restored for a big campaign?

Show the trigger and the uncleared ticket. Campaign pressure is how you re-burn the domain. Fix the rule break, then restore.

How does this relate to Nvidia's announcement?

Kirsten Korosec's Sep 28 TechCrunch piece describes OpenShell and BlueField-4 Sentry quarantining breakout agents in a platform context. GTM steals the control pattern: isolate on breakout, then review. You are not buying a GPU for Outreach.