Repository navigation
mcp-moat 0.2.0
Yanked on crates.io: the Linux binary needs glibc 2.39, and with --no-prompt the block message wrongly says the operator rejected the call. Use 0.2.2 or later.
Added
moat checkvalidates a configuration without starting a server: TOML syntax,allowed_paths(must exist and be directories), the audit log path and theblocked_commands_regexentries.moat completion bash|zsh|fish|powershellprints shell completions.- Secret masking knows more formats: OpenAI
sk-proj-,sk-svcacct-andsk-admin-keys, DeepSeek, Mistral and Cohere (with context), Perplexity, Voyage AI, AWS temporary session keys (ASIA...) and AWS secret access keys next toawsorsecret. dlp_base64_heuristicinmoat.toml(defaultfalse). When on, long Base64 and Base64url runs with upper case, lower case and digits are masked as possible secrets. It is off by default because it also masks image and audio data, file paths, lockfile hashes, long identifiers and public keys.protected_filesinmoat.toml. The file passed to--configis added automatically, so an agent cannot rewrite the policy that guards it.- The crates are published on crates.io (
cargo install --locked mcp-moat).
Changed
blocked_commandsentries are tokenized before matching: whitespace is collapsed, path prefixes such as/bin/rmare reduced to the program name, combined short flags are compared as sets, andsudois skipped.rm -rf /,rm -r -f /,/bin/rm -fr /andsudo rm -rf /now matchrm -rf /.rm -rf /tmp/builddoes not match and goes to the operator prompt.- The UNC and NT path check also rejects
\GLOBAL??\,\GLOBALROOT\,\DosDevices\,\SystemRoot\,\BaseNamedObjects\,\ArcName\and\KernelObjects\, and normalizes separators first.
Fixed
- Audit writes fail closed. If the audit log cannot be created, opened, written or flushed, the action is not forwarded. Before, the error was logged and the call went through without an audit entry. The experimental SSE bridge stops forwarding events in the same case.
- Audit error messages no longer contain the session id.
moat checkno longer rejects a--configfile orprotected_filesentry whose path has an 8.3-style segment, such as the Windows temp folderC:\Users\RUNNER~1\.... The 8.3 rule is meant for paths in tool calls.
Install
cargo install --locked mcp-moatBinaries for Linux, macOS and Windows are attached below. Check them against SHA256SUMS.