This release is a pre-release and may not be stable for production use.
HellAdmin Server
MCP proxy server + kernel-level enforcement engine for AI agent infrastructure.
Contains:
- Landlock enforcer — unprivileged kernel file/network sandboxing (no root)
- seccomp-bpf — syscall filtering (ptrace, mount, unshare blocked)
- MCP proxy — reverse proxy for MCP servers with argument validation
- ArgumentValidator — blocks command injection, path traversal
- EgressGuard — blocks SSRF to cloud metadata endpoints
- Policy compiler — one YAML config to seccomp + AppArmor + nftables + Landlock rules
- Activity source detection — classify events by SSH session, container, process
Quick start
pip install helladmin
# Sandbox a process
helladmin run -- python3 agent.py
# MCP proxy
helladmin proxy add --name my-server --cmd python3 server.py --access public
helladmin proxy serve --port 8443
# Dashboard
helladmin dashboard --port 8888
Requirements
Linux (kernel 5.13+), Python 3.11+.
License
Apache-2.0
1 maintainer
Metadata
1 maintainer
Release files for helladmin-server 0.1.0a5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| helladmin_server-0.1.0a5-py3-none-any.whl | Python 3 | none | any | Details for helladmin_server-0.1.0a5-py3-none-any.whl |
Release files / helladmin_server-0.1.0a5-py3-none-any.whl
| Download URL | helladmin_server-0.1.0a5-py3-none-any.whl |
|---|---|
| Size | 756.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da2a2023ec0b2261e227f2d2c7c4c0cd573586995907df5d5552fda0c2e19542
|
|
BLAKE2b-256 checksum How to use checksums |
9543931a9939c51f9f30d6f30f220c52e7a785fe4b80993f286b967664a0e9d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for helladmin-server 0.1.0a5
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
