vulnify
Runtime authorization for AI agents. Before the agent exports or sends customer records, your app asks Vulnify. The decision is ALLOW, REVIEW, or BLOCK. The score is an integer from 0 to 100 and comes back with reasons.
Vulnify sees action metadata — agent, action, resource, destination, and record count — not the records. In monitor mode the event is stored and not enforced: obey final_decision when it is present, otherwise decision. evaluated_decision is what enforcement would have returned, and monitored is True. If Vulnify cannot be reached, the default is fail-closed.
Standard library only. Python 3.9+.
Production API: https://api.vulnify.io
Documentation: https://docs.vulnify.io
Install
pip install vulnify
Production scenario
An agent is about to export customer records to an external destination. Call check() first.
ALLOWruns the export.REVIEWstops and tells the caller a human must approve. The export does not run.BLOCKdoes not run the export.- If Vulnify cannot be reached,
check()returnsBLOCKwithdegraded=True. The export does not run.
Set VULNIFY_API_KEY. With no base_url, this calls https://api.vulnify.io. For a local API, set VULNIFY_BASE_URL=http://localhost:3000 or pass base_url="http://localhost:3000". An explicit base_url wins over VULNIFY_BASE_URL.
import os
import sys
from vulnify import Vulnify
def export_customer_records() -> None:
"""Replace the body with the real export. It runs only after ALLOW."""
print("exporting customer records to the external destination")
def main() -> None:
api_key = os.environ.get("VULNIFY_API_KEY")
if not api_key:
raise SystemExit("Set VULNIFY_API_KEY")
# Local API: Vulnify(api_key=api_key, base_url="http://localhost:3000")
vulnify = Vulnify(api_key=api_key)
decision = vulnify.check(
agent="SalesBot",
action="EXPORT_DATA",
resource="Customer Database",
destination="EXTERNAL_EMAIL",
records_affected=12000,
)
if decision.decision == "ALLOW":
export_customer_records()
return
reasons = "; ".join(decision.reasons) or "no reason given"
if decision.decision == "REVIEW":
score = "unknown" if decision.risk_score is None else str(decision.risk_score)
event_id = decision.id or "none"
raise SystemExit(
f"A human must approve this export before it runs (event {event_id}, score {score}). {reasons}"
)
if decision.degraded:
raise SystemExit(f"Vulnify could not be reached. The export was not run. {reasons}")
raise SystemExit(f"Export blocked. The export was not run. {reasons}")
if __name__ == "__main__":
try:
main()
except Exception as err:
print(err, file=sys.stderr)
raise SystemExit(1)
A REVIEW is approved on the Vulnify server (Slack, an MFA step-up, or a separate approver). This process does not approve it and does not poll. A separate MCP or HTTP gateway injects secrets only after ALLOW.
guard(fn, **action) runs fn only when the effective decision is ALLOW and raises VulnifyBlockedError for REVIEW and BLOCK. That effective value is final_decision when the API sent it, and decision otherwise. Pass wait={"timeout": 300} only when you mean to poll until a review resolves. protect(**action) is the same check as a decorator. Retries reuse the same Idempotency-Key, so a retry does not create a second event. get_event and wait_for_review use those same retries; if the API is still unavailable they raise VulnifyError instead of applying fail_mode.
Decisions
ALLOW— run the action.risk_scoreis 0–100.reasonsexplains the score.REVIEW— do not run the action yet.review["status"]starts asPENDING. Tell the caller a human must approve.BLOCK— do not run the action.
decision is the outcome stored on the event. It does not change when a review is resolved. final_decision is the field to obey after a review: REVIEW while it is pending, ALLOW when a human approves, and BLOCK when they deny it or it expires. get_event returns the same body as check(), including final_decision, quota_exceeded, sandbox, and lgpd_categories. An idempotent replay of a decision made before finalDecision shipped can omit it (final_decision is None). wait_for_review and guard(..., wait=) then treat review status APPROVED as the go signal, and DENIED or EXPIRED as a block.
Follow final_decision in monitor mode when it is present, otherwise decision. An invalid API key, an unknown agent or resource, a rejected payload, or a body the API refuses as too large (413) raises VulnifyError. The same is true of any other HTTP 4xx except 408 and 429. fail_mode="open" does not swallow those errors and does not retry them.
Optional content is scanned for sensitive data and is not stored. Matches return on dlp_findings.
Fail-closed
fail_mode defaults to "closed". A timeout, a network error, 408, 429, or a 5xx becomes decision="BLOCK", degraded=True, and a reason beginning with Vulnify unavailable. The scenario above does not call export_customer_records(). Set fail_mode="open" only when an outage should let the action through. A 413 or any other non-retryable 4xx never takes that path.
Audit events are hash-chained. SIEM export is JSON or CEF. Evidence in the product maps to LGPD, ISO/IEC 42001, NIST AI RMF, and the EU AI Act. That mapping is not a certification.
Adapters
vulnify.adapters is duck-typed and does not import a framework until an adapter needs a type from that package. The core install has no runtime dependencies. Samples are in examples/.
CrewAI (guard_crewai_tool, crewai_before_tool_call) and LangGraph (langgraph_tool_guard, alanggraph_tool_guard) take a describe callback that maps tool arguments to check keywords. on_blocked="message" (the default for tool wrappers) returns Vulnify's reasons to the agent. "raise" raises VulnifyBlockedError.
LangChain
pip install 'vulnify[langchain]'
guard_langchain_tool guards _run / _arun on a BaseTool, so invoke checks once. A tool that only has invoke or call is guarded on those methods.
from vulnify.adapters import guard_langchain_tool
export_tool = guard_langchain_tool(vulnify, export_tool, describe_export)
OpenAI Agents
pip install 'vulnify[openai-agents]'
guard_openai_agents_tool wraps a Python FunctionTool. describe sees the parsed JSON arguments. The model receives the block text instead of the tool running. on_blocked="raise" rethrows.
from agents import function_tool
from vulnify.adapters import guard_openai_agents_tool
@function_tool
def export_customers(rows: int) -> str:
"""Export customer records."""
return f"exported {rows}"
export_customers = guard_openai_agents_tool(vulnify, export_customers, describe_export)
MCP
pip install 'vulnify[mcp]'
guard_mcp_handler wraps a tool function before you register it on MCPServer (mcp 2; the older name was FastMCP). guard_mcp_client wraps session.call_tool. A blocked call returns an MCP error result (CallToolResult when mcp is installed) and does not raise VulnifyBlockedError. Tools omitted from the client describe map are forwarded unchanged.
from mcp.server import MCPServer
from vulnify.adapters import guard_mcp_client, guard_mcp_handler
async def export_customers(rows: int) -> str:
"""Export customer records."""
return f"exported {rows}"
server = MCPServer("sales")
server.tool()(guard_mcp_handler(vulnify, describe_export, export_customers))
session = guard_mcp_client(vulnify, session, {"export_customers": describe_export})
A REVIEW uses final_decision on every adapter: ALLOW runs the tool, and BLOCK does not.
The npm SDK also ships a Vercel AI SDK helper. That framework has no Python counterpart, so this package does not include it.
Webhooks
Vulnify signs each delivery with HMAC-SHA256. The key is the endpoint secret as UTF-8, including the whsec_ prefix. It is not base64-decoded. The signed message is the unix timestamp, a dot, and the raw body bytes. X-Vulnify-Signature looks like t=<unix seconds>,v1=<hex>. During a secret rotation the header can carry more than one v1; any match is enough. A timestamp exactly 300 seconds off is still valid. Pass the raw body, not JSON you parsed and dumped again.
X-Vulnify-Delivery is the delivery id (event.id). Dedupe retries on it. X-Vulnify-Attempt starts at 1. X-Vulnify-Event is the primary type and matches event.type. Those three headers are not signed. Trust the body after the signature check.
from vulnify import WebhookVerificationError, construct_webhook_from_request
try:
event = construct_webhook_from_request(secret, headers, raw_body)
except WebhookVerificationError:
return 400 # 408, 429, and 5xx are retried; any other 4xx stops them
# event.id is the delivery id. event.event_id is the security event, anomaly, or test id.
if event.type in ("BLOCK", "REVIEW", "CRITICAL"):
obey = event.data.final_decision # ALLOW, REVIEW, or BLOCK
verify_webhook_signature(secret, signature_header, raw_body) only checks the signature and raises WebhookVerificationError. parse_webhook(raw_body) returns a DecisionWebhook, AnomalyWebhook, or TestWebhook. construct_webhook does both. decision on a decision payload is what was stored. final_decision is the outcome to obey.
Flask uses request.get_data(), FastAPI uses await request.body(), and Django uses request.body. Short samples are in examples/flask_webhook.py, examples/fastapi_webhook.py, and examples/django_webhook.py.
Development
pip install -e ".[dev]"
pytest
License
MIT. Copyright 2026 Vulnify.
Metadata
Release files for vulnify 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 | |
|---|---|---|---|
| vulnify-0.3.1.tar.gz | 22.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vulnify-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.6 kB
Release files / vulnify-0.3.1.tar.gz
| Download URL | vulnify-0.3.1.tar.gz |
|---|---|
| Size | 22.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08f8d19ffcc567260d188e4adb6c48b52a46ce657066bf1de4c45ae9fd1ff466
|
|
BLAKE2b-256 checksum How to use checksums |
bffcb13f3f108d538a7b68f0c6a3ad2c2330b5dd1adaadeadbb475a1cc950e39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 2, 2026.
Transparency logRelease files / vulnify-0.3.1-py3-none-any.whl
| Download URL | vulnify-0.3.1-py3-none-any.whl |
|---|---|
| Size | 20.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de6ade5e6652e4080a52f8b4ace0d21a91b3e1d6fae1ae32b979c9782f93bd1a
|
|
BLAKE2b-256 checksum How to use checksums |
04f5ca2ed037ca649b95e2813e8d0877c79f4e7a0981ccfbf87d17b88759b797
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 2, 2026.
Transparency log