HiveKey
Home/ Enforcement/ Quarantine & step-down
Enforcement · Containment

Quarantine & step-down.

Step a breaching agent down to read-only instead of killing it outright.

in the path

// policy

trigger → role = read-only + flag(review)

agent stepped down → read-only review
Why it matters

A full kill can take down work that was fine alongside the part that wasn't. Sometimes the right move is to shrink the blast radius, not pull the plug.

How it works

When an agent breaches, drop it into a minimal read-only mode rather than cutting it off entirely, so it can keep doing harmless work while you investigate.

01

Intercept

The agent attempts an action. HiveKey catches it in the path — nothing reaches the tool yet.

02

Evaluate

On a trigger, HiveKey swaps the agent's role for a minimal read-only one in the path and flags it for review, with the step-down recorded in the log.

03

Enforce & log

The verdict is enforced — allow, block, or route for approval — and written to the audit trail, attributable to the agent's owner.

Agent

attempts an action

HiveKey

scope · guard · log

Tool / MCP

only allowed actions

What you get

Built for security and platform teams.

Contain a breach without the collateral of a full kill

Drop the agent to a minimal, read-only role

Flag it for review while harmless work continues

Part of Guard

Quarantine & step-down is one expression of Guard.

Every capability rides the same spine — Scope what an agent can do, Guard each action in the path, Log all of it on one trail.

Explore Guard

Enforce every action your agents take.

Scope, guard, and log every action — and enforce it in the path, before anything happens.