HVT

Decide what agents may do

Authority is granted per action, bounded by execution envelopes, and revocable instantly./Agents only do what you allow, and you can switch them off in one click.

Architecture term (Salem Salah bin Omair AlShamsi)/Plain English

Connected does not mean authorised. HVT gives each agent an authority graph and an execution envelope that caps rate, spend, geography and blast radius./Being plugged in does not mean being allowed. Each agent gets clear limits on speed, spending, reach and how much damage it could do.

BudgetPer agent
High riskNeeds approval
RevokeOne click
The problem

What goes wrong without it

01

Many individually permitted acts can sum to one forbidden outcome./Lots of small allowed steps can add up to one big bad result.

02

High-risk actions execute without a named human approver./Risky actions happen with nobody signing off.

03

A misbehaving agent cannot be revoked quickly./When an agent goes wrong there is no fast off switch.

How HVT handles it

Four steps, in order

1

Register

Each agent is inventoried with a risk tier and owner./Every agent is listed with an owner and a risk level.

2

Bound

Execution envelopes cap tool calls per window./Each agent gets a limit on how much it can do in a period.

3

Approve

High-risk acts are held in SAFE HOLD for a signed human decision./Risky actions wait for a person to say yes.

4

Revoke

A kill switch withdraws credentials at once./One click takes the agent's access away.

What you get

Key capabilities

Tool-call budgets

Circuit breaker trips when the envelope is exceeded./Too many calls and the agent is paused.

Approval queue

Approvals bind to a named principal./A real person's name is on every approval.

Kill switch

Revocation propagates cryptographically./Switching off works everywhere, immediately.

Risk tiers

Controls scale with the agent's tier./Riskier agents get stricter rules.

Example

Before and after

Without HVT

A finance agent issues refunds in a loop until the budget is gone./A finance agent keeps refunding money until there is none left.

With HVT

The budget breaker blocks the 15th call; one large refund waits in the approval queue./It is stopped after its limit, and the big refund waits for a person.

Illustrative scenarios. Controls shown are design intent, confirmed by the gates on your own infrastructure.