Write the boundary
Declare skills, policies, allowed and blocked actions in a versioned YAML file your whole team can review in a pull request.
Agent Registry is a declarative policy layer for AI agents. One YAML file defines what an agent may do, what is blocked, what needs approval and what it may spend - enforced at runtime, before any side effect happens.
pip install hlinor-registry - Python 3.10-3.13, 50+ automated tests, CI matrix on every change.
Your agent can call tools, spend API budget and touch customer data. Today that boundary lives in prompts and good intentions. When something goes wrong, nobody can show what the agent was allowed to do - or prove it stayed inside.
Four steps from intent to enforced boundary.
Declare skills, policies, allowed and blocked actions in a versioned YAML file your whole team can review in a pull request.
The CLI compiles YAML into a signed, deterministic bundle. Static linting catches contradictions before deployment.
Wrap existing tools with a decorator or framework integration. A denied action simply does not execute and returns a machine-readable reason code.
Every allow/deny decision lands in a JSONL log, ready for Splunk, Datadog or your auditor.
Block external email, record mutation and other exfiltration paths for agents handling sensitive data.
Declare budgets, rate limits and approval requirements beside the agent definition - and enforce them.
Hand enterprise buyers a signed policy bundle and decision log instead of a promises document.
Agent Control Plane scans your actual codebase and runtime to check that what is deployed matches what you declared.
Our Agent Governance Review checks your agent policies, runtime permissions and audit trails - and delivers a client-ready report in 72 hours.