amanai
Action Policy Engine for AI agents — policy-as-code for tool-calls. Pure-Python, zero dependencies.
Write one policy for risky agent actions. Amanai evaluates every tool-call against it before the tool runs, enforces the decision, and records a structured trace as evidence. The same policy file asserts in CI — what you test is what you enforce. Decisions are deterministic: no LLM decides whether a high-risk tool runs.
pip install amanai
Action Policy Engine
Five verbs: load a policy, evaluate an action, protect a tool, collect a trace, assert it in tests.
from amanai import set_policy, tool, ToolBlocked, ApprovalRequired, collect_trace
set_policy("amanai.policy.json") # load + validate (raises PolicyError if bad)
@tool(name="billing.refund", capability="money_movement", risk="high")
def refund_payment(amount): ...
refund_payment(amount=500) # ToolBlocked / ApprovalRequired per policy
trace = collect_trace() # canonical evidence: action + decision + status
A policy is a list of rules. A rule matches on tool and/or capability,
with optional args and context predicates, and carries an action:
[
{ "id": "discount-cap", "tool": "apply_discount",
"args": [{ "arg": "pct", "op": ">=", "value": 50 }],
"action": "block", "reason": "discount of 50% or more is never allowed" },
{ "id": "refund-approval", "tool": "refund_payment",
"args": [{ "arg": "amount", "op": ">", "value": 100 }],
"action": "require_approval" },
{ "id": "external-email", "capability": "external_comms",
"args": [{ "arg": "to", "op": "email_external", "value": ["acme.com"] }],
"action": "block" }
]
- Outcomes:
allow·block·warn·require_approval. - Operators:
>= > <= < == !=·contains·regex·in/not_in·email_external·domain_in/domain_not_in. - Modes (per request, never global):
enforceblocks before execution ·shadowrecords what it would block but lets the call run ·testevaluates with no side effects. - The legacy flat rule
{tool, arg, op, value}still loads (it defaults toblock). Rules without anidget a deterministic generated one.
from amanai import set_mode, set_context, evaluate, ActionRequest
set_mode("shadow") # observe before enforcing
set_context(role="support", tenant="t1", environment="prod") # authz context for rules
evaluate(ActionRequest("apply_discount", {"pct": 90})) # -> PolicyDecision(outcome="block", ...)
Assert the same policy in CI
from amanai.testing import assert_blocked, assert_no_violations
def test_excessive_discount_is_blocked():
set_policy("amanai.policy.json")
assert_blocked(apply_discount, pct=90)
def test_attack_trace_is_clean():
run_agent(attack_prompt) # produces a trace
assert_no_violations(collect_trace()) # replays actions against the active policy
amanai.testing also ships assert_requires_approval,
using_mode, and replay (re-evaluate a recorded trace against a policy).
Runtime guardrails (input / output, supporting)
from amanai import guard_input, guard_output, GuardrailBlocked
try:
msg = guard_input(user_msg) # raises GuardrailBlocked on injection
except GuardrailBlocked:
reply = "I can't help with that."
else:
reply = guard_output(run_agent(msg)) # redacts emails, cards, secrets
Offline judge & MCP checks (supporting)
Score an agent's input / response / tool-calls against detectors (string match,
tool assertions, MCP checks; LLM-as-judge when you pass a gateway). The
tool_assertion detector reuses the engine's operators, so the test side can't
drift from runtime — a contract test guarantees it.
Monitoring (optional — needs an Amanai server)
from amanai import Monitor, collect_trace
mon = Monitor("http://localhost:8000", PUBLIC_KEY, SECRET_KEY)
mon.log_trace(collect_trace(), user_id="u123") # canonical events, PII redacted
API
- Engine:
load_policyset_policyget_policyevaluatePolicyRuleActionRequestPolicyDecisionTraceEventPendingActionPolicyError - Modes / context:
set_modeget_modeset_contextget_contextclear_context - Protect / collect:
toolcollect_tracecollect_tool_callsrecord_tool_callresetregistered_toolsuncovered_toolsToolBlockedApprovalRequired - Test:
amanai.testing—assert_blockedassert_requires_approvalassert_no_violationsusing_modereplay - Policy lifecycle:
clear_tool_policy(deactivate the active policy) - Guardrails:
guard_inputguard_outputredact_piidetect_injectiondetect_piiGuardResultGuardrailBlocked - Judge / monitor:
judgeMonitor
Apache-2.0. Zero runtime dependencies.
Metadata
Release files for amanai 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| amanai-0.3.1.tar.gz | 31.9 kB | With provenance | Details for amanai-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| amanai-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for amanai-0.3.1-py3-none-any.whl |
Total release size: 74.1 kB
Release files / amanai-0.3.1.tar.gz
| Download URL | amanai-0.3.1.tar.gz |
|---|---|
| Size | 31.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1def662e01b258defdc6321ec619a476732506d8ee1a2251572ab6d6c8350eee
|
|
BLAKE2b-256 checksum How to use checksums |
fd5c3cc0b113d2139ec5f0650edf8213d60f40e20f602001e44b32b21d9294e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 2, 2026.
Transparency logRelease files / amanai-0.3.1-py3-none-any.whl
| Download URL | amanai-0.3.1-py3-none-any.whl |
|---|---|
| Size | 42.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7d212eaaeb7fff51e7397456ba61442a8bf5060d5f51559f8bfeeabcb46980a
|
|
BLAKE2b-256 checksum How to use checksums |
ebdeaa4ea782af47d9d5a1f3cd5a32c2dc9fd0439ca10187dc57413a3a3a0644
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 2, 2026.
Transparency logSecurity for amanai 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for amanai-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.