llama-index-trust-gate
LlamaIndex tools for Trust Gate: signed receipts for agent actions, a read-only-allowlist decision gate, an egress marker check and an exit drill.
Receipts are signed by the hosted MCP server (no local signing key) with Ed25519, plus ML-DSA-65 when the server has a post-quantum backend. A receipt's integrity can be checked offline. To know which key signed it, verify with expected_kid (the kid of the server you trust): without that, anyone can generate keys and sign a receipt that verifies. The server defaults to PQ-required verify (a receipt with no verified post-quantum signature is rejected); set TRUST_GATE_REQUIRE_PQ=false on your own deployment to allow Ed25519-only receipts.
Install
pip install cwn-llama-index-trust-gate
Usage
from llama_index.core.agent import ReActAgent
from llama_index_trust_gate import mint_action_receipt_tool, verify_receipt_tool
agent = ReActAgent.from_tools(
[mint_action_receipt_tool(), verify_receipt_tool()],
llm=...,
)
Tools
| Factory | Name | Purpose |
|---|---|---|
mint_action_receipt_tool() |
trust_gate_mint_action_receipt |
Mint a signed receipt (Ed25519, plus ML-DSA-65 when the server has a post-quantum backend) for a consequential agent action. |
verify_receipt_tool() |
trust_gate_verify_receipt |
Verify a receipt offline. Pass expected_kid to pin the signer; the result reports signer_pinned. |
gate_decision_tool() |
trust_gate_gate_decision |
Two-phase gate (server 0.3.0 or later). PREVIEW returns a verdict (ALLOW, DENY, ESCALATE); COMMIT signs a receipt and returns a permit, GRANTED only for ALLOW. It judges names against a read-only allowlist and does not observe or block anything. |
check_egress_tool() |
trust_gate_check_egress |
Check data for sensitivity markers (NO_MARKERS_FOUND / INTERNAL / CONFIDENTIAL / RESTRICTED) before it leaves. It flags and cannot block. |
run_exit_drill_tool() |
trust_gate_run_exit_drill |
Vendor exit-readiness drill: checks the local signing key and whether a local model endpoint is configured. It signs a receipt, which creates the signing key on first use. |
Configuration
export TRUST_GATE_URL="https://trust-gate-mcp.onrender.com" # default; override for self-hosted
Compatibility
This release is written for Trust Gate MCP server 0.3.0 or later. Versions before 0.3.0 of the server's gate_decision returned GRANTED for every input: treat any GRANTED permit from a server older than 0.3.0 as not evidence. See the security advisory.
Passing expected_kid to a server older than 0.3.0 raises an error: those servers ignore the argument and would otherwise return ok without checking the signer.
Telemetry
One fire-and-forget GET /x?via=llamaindex&kind=api per tool call. No PII, no cookies, never blocks the tool.
Related
- langchain-trust-gate -- same tools, LangChain shape
- crewai-trust-gate -- same tools, CrewAI shape
- Trust Gate MCP -- the hosted server: https://trust-gate-mcp.onrender.com
License
Apache-2.0.
Metadata
Release files for cwn-llama-index-trust-gate 0.3.0
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 |
|---|---|---|---|---|
| cwn_llama_index_trust_gate-0.3.0.tar.gz | 8.6 kB | With provenance | Details for cwn_llama_index_trust_gate-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cwn_llama_index_trust_gate-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for cwn_llama_index_trust_gate-0.3.0-py3-none-any.whl |
Total release size: 16.5 kB
Release files / cwn_llama_index_trust_gate-0.3.0.tar.gz
| Download URL | cwn_llama_index_trust_gate-0.3.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07f92afe431155f1df81cd7ec992e472062fdeab8e2fa578a80ae491ed83b0fd
|
|
BLAKE2b-256 checksum How to use checksums |
feebc08327f00e005cc2b988b4b6695141e9830663df1afc61febe6b0001d8b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 / cwn_llama_index_trust_gate-0.3.0-py3-none-any.whl
| Download URL | cwn_llama_index_trust_gate-0.3.0-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd728129d5f1a1ae50b0a509e2312b272f45bebdff3dac5976702054ea8914c6
|
|
BLAKE2b-256 checksum How to use checksums |
fa29307d625973f8962b59a8198737f3b5edac10a979ce13dee1f9c6fced7890
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 logSecurity for cwn-llama-index-trust-gate 0.3.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for cwn_llama_index_trust_gate-0.3.0.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 Oct 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.