Pandaone Guard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NO_COLOR | No | Set to 1 to disable colored output | |
| PANDAX_LANG | No | UI language (zh / en) | zh |
| PANDAX_FP_PASSWORD | No | Only needed for pandaone_fingerprint_update / pandaone_watch daemon auth; set locally, never uploaded | 0000 |
| PANDAONE_SKIP_GIT_CHECK | No | Set to 1 to skip git detection (for git-less environments) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pandaone_initB | 在指定目录初始化 Pandaone AI Agent（创建 .pandaone/、config.json、pandaone.jsonl、可选 binary_snapshots.json） |
| pandaone_lockB | 锁定所有受保护扩展名的文件（attrib +r / chmod -w） |
| pandaone_unlockC | 解锁所有受保护扩展名的文件 |
| pandaone_writeA | 审计写入（核心命令）：reason/problem/approach 必填；文本用 --old/--new 或 --content；二进制用 --from-file 或 --content-base64。目标文件不存在时视为创建新文件（须提供内容且扩展名受保护，action=create） |
| pandaone_logB | 查看审计日志（按文件/recent/格式过滤） |
| pandaone_statusB | 查看 Pandaone 状态（保护文件 / 审计次数 / 锁定状态等） |
| pandaone_install_hookB | 安装/卸载 pre-commit hook |
| pandaone_watchB | 启动 watchdog 守护进程（监控文件改动） |
| pandaone_install_gitA | 安装便携版 git（用于项目内 git hook，无需全局 git） |
| pandaone_fingerprint_updateA | 更新密码指纹（用于 watch 守护进程鉴权） |
| pandaone_ciA | CI 审计验证：对比 base..head 的所有改动，确认每条变更都通过 pandaone write 审计 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a largely distinct purpose: initialization, audited writes, lock/unlock, logging/status, hook/watch setup, portable git install, fingerprint update, and CI verification. Minor boundary overlap exists between status and log viewing, and between hook/git installation tools, but descriptions clarify the intended use.
All tools consistently use the pandaone_ prefix with snake_case, making the set easy to scan. However, the pattern mixes verbs, nouns, and abbreviations rather than following a strict verb_noun convention.
With 11 tools, the set is well-scoped for a file audit and protection system. Each tool appears to earn its place by covering a distinct operational area without excessive fragmentation.
The surface covers the core lifecycle: init, audited write/create, lock/unlock, logs, status, hooks, watchdog, git setup, fingerprint update, and CI verification. Minor gaps remain around explicit configuration/protected-extension management, manual verification outside CI, and cleanup/uninstall workflows.