Skip to content

Releases: JUSICK/Argos-mcp-guardrail

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 13 Oct 21:22

Fixes the sample argos.toml in the v0.2.0 downloads. It was missing
.npmrc, .aws and .git-credentials from blocked_patterns and
rm -fr from blocked_commands. Because a list in argos.toml replaces
the default list, keeping that file next to the binary gave you weaker
rules than having no config at all.

If you installed v0.2.0 from an archive, either replace its argos.toml
with the one from this release or delete it to use the built-in defaults.
The program itself hasn't changed since v0.2.0. See the
v0.2.0 notes
for what's new since v0.1.1, including the --workspace flag.

The repo now has a LICENSE file (MIT), and the README has been rewritten.

File For
argos.exe, argos-windows-x86_64.zip Windows x86-64
argos, argos-linux-x86_64.tar.gz Linux x86-64, any distro
argos-macos-universal.tar.gz macOS, Apple Silicon and Intel

Checksums are in SHA256SUMS.txt. The macOS binary isn't signed, so run
xattr -d com.apple.quarantine argos once after extracting.

v0.2.0

Choose a tag to compare

@JUSICK JUSICK released this 13 Oct 20:48

Before you upgrade

Two changes can stop an existing setup from starting:

  • Add --workspace <folder> before -- in your client config:

    "args": ["--workspace", "C:\Users\you\projects\my-project", "--",
             "npx.cmd", "-y", "@modelcontextprotocol/server-filesystem", "C:\Users\you\projects\my-project"]

    Without it Argos still uses the last directory in the server arguments,
    but it now refuses to start if there isn't one or if it's / or C:\.
    It used to fall back to the current directory, which could be anything.

  • A broken argos.toml now stops Argos with the error instead of being
    ignored. That includes misspelled keys. No file still means defaults.

Security fixes

  • A folder next to the workspace whose name starts the same way
    (C:\ws-evil next to C:\ws) was treated as inside it.
  • The audit log stored full tool arguments, so a blocked write of a .env
    file put the secret itself in the log. Only paths are logged now; other
    values are [REDACTED]. On macOS and Linux the log is created readable
    only by you.
  • A single huge input line could use unlimited memory. Lines over 8 MiB now
    end the session.
  • Replies the server was still sending when the client disconnected were
    dropped. Argos now waits for them (up to 30 seconds).
  • The last audit log entries before shutdown could be lost.

Other changes

  • Audit entries include argos_pid and server_pid.
  • rm -fr is blocked by default.
  • macOS builds (universal, Apple Silicon and Intel).

Downloads

File For
argos.exe, argos-windows-x86_64.zip Windows x86-64
argos, argos-linux-x86_64.tar.gz Linux x86-64, any distro
argos-macos-universal.tar.gz macOS, Apple Silicon and Intel

Checksums are in SHA256SUMS.txt. The macOS binary isn't signed, so run
xattr -d com.apple.quarantine argos once after extracting.

The argos.toml inside these archives is missing a few of the default
rules (.npmrc, .aws, .git-credentials, rm -fr). Use
v0.2.1
instead, which ships the corrected file.

v0.1.1 — Path Canonicalization & Expanded Security Defaults

Choose a tag to compare

@JUSICK JUSICK released this 06 Oct 18:02

Expended Security Default Patterns:

  • .aws,
  • .npmrc

Path Canonicalization:

  • Applying deny rules only after resolving relative paths and symlinks

v0.1.0 - Lightweight Zero-Latency Security Gateway for MCP

Choose a tag to compare

@JUSICK JUSICK released this 04 Oct 16:50

ADDED:

  • audit log,
  • blocked_patterns,
  • allowed_patterns,
  • blocked_commands,
  • block_path_traversal