rustpanosmcpSAFE
Async Rust MCP server for Palo Alto Networks PAN-OS firewalls — bearer-token auth, per-token device/tool scopes, guarded candidate-config lifecycle
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
rust-panosmcp
Async Rust Model Context Protocol server for Palo Alto Networks PAN-OS firewalls a mechub project — sovereign network-security automation
Unofficial / community project. This is an independent community project and does not claim affiliation with or endorsement by Palo Alto Networks. Product names and trademarks are used only to identify the systems with which the software interoperates.
The repository contains the v0.16.0 release: a bearer-protected server with structured audit logging, guarded PAN-OS candidate configuration lifecycle, and hardened release packaging, with authentication and auditing provided by the shared `mecmcp-auth` and `mecmcp-audit` crates.
The project goal is a small, fast, production-oriented server with the same security posture as rust-junosmcp: bearer-token authentication, per-token device and tool scopes, TLS, strict remote-bind refusal rules, bounded input and output, auditable change operations, and efficient connection reuse.
The architecture and delivery plan are in PLAN.md. Security boundaries and release-blocking controls are tracked in THREAT_MODEL.md.
Workspace
rust-panosmcp/ # MCP binary and stdio adapter rust-panosmcp-auth/ # bearer and secret-handling foundations rust-panosmcp-core/ # inventory, PAN-OS client, validation, tool logic config/ # secret-free inventory examples docs/ # operator guidance and phase notes fuzz/ # isolated cargo-fuzz workspace packaging/ # distroless/container and systemd assets scripts/
6d52c6cabb2cOBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add rustpanosmcp:0.16.0 -- docker run -i --rm ghcr.io/mechubsec/rustpanosmcp:0.16.0:None stdio
Trust audit
SAFEgrade B · trust 84/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (5 observation(s))
- Network
- declared (3 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- found
Findings (17)
"-----BEGIN RSA PRIVATE KEY-----\n",
.gitleaks-vendor.toml
.gitleaks.toml
PACKAGE_ROOT="$(cd -- "$SCRIPT_DIR/../../.." && pwd -P)"
PACKAGE_ROOT="$(cd -- "$SCRIPT_DIR/../../.." && pwd -P)"
PACKAGE_ROOT="$(cd -- "$SCRIPT_DIR/../../.." && pwd -P)"
PACKAGE_ROOT="$(cd -- "$SCRIPT_DIR/../../.." && pwd -P)"
PACKAGE_ROOT="$(cd -- "$SCRIPT_DIR/../../.." && pwd -P)"
The installer creates the `rust-panosmcp` user and directories via `systemd-sysusers` and `systemd-tmpfiles`, installs the binary and unit, creates an empty `tokens.json` with mode 0600, and never ove
"endpoint": "https://192.0.2.20",
--allowed-origin http://127.0.0.1:30031 --allowed-origin http://localhost:30031
The `--allowed-origin http://127.0.0.1:30031` values are a working local default
--allowed-origin http://127.0.0.1:30041 --allowed-origin http://localhost:30041 \
File holding the read identity's password. Must be 0600
- **Rate limiting now uses a token-bucket algorithm instead of a fixed sliding window**, via the shared [`mecmcp-transport`](https://github.com/mechubsec/mecmcp) crate (`transport-v0.1.6`). The CLI fl
The MCP endpoint is `https://mcp.example.test:30031/mcp`. Send the token as
Gates applied: no_behavioural_pass.
6d52c6cabb2cfull audit observations/trust-audit/mcp-server/mechubsec__rustpanosmcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | 6d52c6cabb2c | SAFE | B | 84 | first audit |
Questions
What is the rustpanosmcp MCP server?
Async Rust MCP server for Palo Alto Networks PAN-OS firewalls — bearer-token auth, per-token device/tool scopes, guarded candidate-config lifecycle
Is rustpanosmcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (84/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does rustpanosmcp need?
No credential environment variables were found in its source, so it appears to need none.
How does rustpanosmcp run?
It speaks stdio and streamable-http, so it runs as a local process your client starts.
How current is this page?
The grade is for one exact copy of the source (6d52c6cabb2c), read on 2026-10-11. The repository is watched and re-audited when it changes.