Skills/Glama/opnsense-guard-mcp

opnsense-guard-mcp@0.1.1

VERIFIED· not started

Publisher claims: "Enables AI clients to inspect OPNsense 26.7+ firewall state and, with policy and a separate write-capable API user, plan, approve, apply, verify, and automatically revert firewall rule and alias changes under hash-chained auditing." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher d3ltasecurity · publishing for 19 daysInstalls 0Last detonated 12 h ago
$npx skills add opnsense-guard-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
OPNSENSE_GUARD_TOKENS_FILEOPNSENSE_WRITE_API_KEYOPNSENSE_WRITE_API_SECRETConfiguration, not credentials: MCP_TRANSPORT, OPNSENSE_GUARD_DATA_DIR, OPNSENSE_GUARD_ENV_FILE, OPNSENSE_GUARD_POLICY
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for OPNSENSE_GUARD_TOKENS_FILE, OPNSENSE_WRITE_API_KEY, OPNSENSE_WRITE_API_SECRET and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandDockerfile:12 · File permission modification command — agent changes file ownership/permissions&& mkdir -p /data && chown guard /dataFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
Access to sensitive file pathstests/test_config.py:59 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file = tmp_path / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/opnsense_guard/config.py:46 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Minimal .env loader. Real environment variables always win."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
MCP server using network transport (SSE/HTTP)src/opnsense_guard/http.py:117 · MCP server using network transport (SSE/HTTP) — data sent over networkdef build_http_app(mcp: MCPServer, settings: HttpSettings, store: TokenStore) -> ASGIApp:Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
HIGH
Access to sensitive file pathssrc/opnsense_guard/server.py:189 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileshelp="optional .env file to load (default: ./.env)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsDockerfile:2 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# docker run -i --rm --env-file .env -v guard-data:/data opnsense-guard-mcpFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Destructive file system command detectedDockerfile:14 · Destructive file system command detectedRUN pip install --no-cache-dir /tmp/*.whl && rm /tmp/*.whlFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
LOW
URL to a private-network addresstests/test_planner.py:237 · URL to a private-network address — a LAN or development targetsettings = ReadSettings(url="https://192.168.60.1:8443", api_key="k", api_secret="s")Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
HIGH
Access to sensitive file pathssrc/opnsense_guard/server.py:188 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdefault=Path(os.environ.get("OPNSENSE_GUARD_ENV_FILE", ".env")),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/opnsense_guard/config.py:1 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Settings, loaded from environment variables (and an optional .env file).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
LOW
URL to a private-network addresssrc/opnsense_guard/config.py:34 · URL to a private-network address — a LAN or development targetraise ValueError("OPNSENSE_URL must include a scheme, e.g. https://10.0.0.1")Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
MEDIUM
MCP server using network transport (SSE/HTTP)src/opnsense_guard/http.py:137 · MCP server using network transport (SSE/HTTP) — data sent over networkdef run_http(mcp: MCPServer, settings: HttpSettings) -> None:Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

Cost to the agent

Instructions loaded
≈43 tok
1 file · 48 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

opnsense-guard-mcp@0.1.1 safety verdict: Verified (not started) — KillerSkills