01 / PRIVACY
Prevent PII leaks
Block external email, record mutation, or other exfiltration paths for agents handling sensitive data.
OPEN-SOURCE CONTROL LAYER / PYTHON 3.10+
Define what your AI agents can and cannot do before they act. Lightweight, open-source, and framework-agnostic.
One reviewable contract. One decision before side effects.
599
automated tests
3.10–3.13
Python CI matrix
Apache 2.0
open-source license
Keep governance close to the code, readable in a pull request, and enforceable at runtime.
id: my-agent
type: agent
name: My First Agent
department: engineering
allowed_actions:
- read_database
- read_database:reports/*
- refund_payment:order/*
blocked_actions:
- send_external_email
policies:
- refund-needs-approval
enforcement_mode: strict
Governance that answers the hard questions early.
01 / PRIVACY
Block external email, record mutation, or other exfiltration paths for agents handling sensitive data.
02 / COST
Keep search counts, premium calls, budget checks, and rate limits visible beside the agent definition.
03 / EVIDENCE
Build an audit trail around approvals, execution receipts, policy decisions, and evidence-bound claims.
Registry files become a shared contract between the people who design agent capabilities and the systems that execute them.
Start with a YAML contract, add a policy check before the first side effect, and invite your security team into the review.
OPEN SOURCE / EARLY ACCESS
HlinorAI works with teams designing internal agent platforms, compliance workflows, and production action boundaries.
Open an issue or start a discussion ↗