poly-queue-mcp

The server utilizes Deno's `Deno.Command.run` to interact with external CLI tools (`redis-cli`, `nats`). While `Deno.Command` mitigates typical shell injection by passing arguments as a string array, potential vulnerabilities could exist if these underlying CLIs interpret specific argument values maliciously. RabbitMQ interaction is via its Management HTTP API. The `lib/resilience.js` module exposes diagnostic information that could lead to information disclosure if the MCP server itself is not secured by an upstream authentication/authorization layer. The project's `SECURITY.md` outlines strong container security, CI/CD security, and code security practices, including the use of Chainguard Wolfi, non-root users, SHA-pinned actions, SAST/DAST, and strict secret management. Environment variables are used for credentials, avoiding hardcoded secrets. The Deno runtime permissions (`--allow-net`, `--allow-read`, `--allow-write`, `--allow-env`, `--allow-run`) are broad but necessary for its function.