HiveKey
Home/ Enforcement/ Rate limits
Enforcement · Core enforcement

Rate limits.

Bound how fast and how often an agent can act.

in the path

// policy

tool.calls ≤ 20 / hour / agent

chat_post (21st in an hour, cap 20) deny
Why it matters

A retry storm or a looping agent can hammer a tool or a vendor API into the ground in seconds, burning your quota and taking the downstream system down with it.

How it works

Hold an agent to a sane call rate — a set number of actions per minute or hour, scoped to one tool or across everything it does.

01

Intercept

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

02

Evaluate

Guard counts calls in a sliding window in the path and slows or blocks the agent the moment the rate is exceeded, before the downstream tool is ever hit.

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 loops and retry storms before they spread

Protect downstream tools and vendor API quotas

Per-tool or fleet-wide limits, set per agent

Part of Guard

Rate limits 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.