HiveKey
Home/ Enforcement/ Policy dry-run & simulation
Enforcement · Operations

Policy dry-run & simulation.

See exactly what a policy would do against real traffic before it enforces.

in the path

// policy

mode: shadow → report would-be verdicts

candidate policy: 3 denies / 1,204 calls review
Why it matters

The thing that stops teams from enforcing is the fear of breaking production. Dry-run replaces that guesswork with the actual verdicts the policy would have produced.

How it works

Run a new or changed policy in shadow mode against live agent traffic and see precisely what it would have allowed and denied — before you turn enforcement on.

01

Intercept

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

02

Evaluate

HiveKey evaluates the candidate policy on real calls in the path and reports the would-be verdicts, without touching the live decision that's actually in effect.

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.

Test a policy on real traffic before it enforces

See exactly what it would allow and what it would deny

Turn on enforcement without gambling on prod

Part of Log

Policy dry-run & simulation is one expression of Log.

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 Log

Enforce every action your agents take.

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