cmdxray
Related Servers
Alternatives to cmdxray
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that vets LLM-emitted shell commands BEFORE execution — detects rm -rf nested deep in chains, package-manager glob removal (apt remove 'nvidia'), dd/mkfs filesystem destruction, chmod 777 / chown -R privilege blast, network-exfil via curl | bash, chained shutdown/reboot, git destructive ops. 30 detection rules across 8 families. Sub-second, local, free, MCP-native.358 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to assess the risk of shell commands before execution, providing a probability of harm and a suggested action (auto, warn, or confirm).MIT

aperion-shieldofficial
FlicenseAqualityAmaintenanceLocal guardrail proxy for AI coding agents. Wraps any MCP server (stdio or HTTP/SSE) and blocks destructive tool calls before they execute, with TOFU catalog pinning against rug pulls and tool-poisoning/result-injection scanning. Single Rust binary, Apache-2.0.1411-- AlicenseNot gradedqualityAmaintenanceA runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.1MIT
- AlicenseAqualityBmaintenanceA consequence engine for shell commands. Blast Scope scores what a command would actually do before an AI agent runs it.454 PyPIApache 2.0
- AlicenseAqualityBmaintenanceEnables agents to score, inspect, and gate tool calls before they execute, resolving shell commands the way a shell would in order to block destructive actions and detect multi-step attack sequences. It also redacts credentials and PII in either direction, requires signed single-use approval tokens for high-impact actions, and keeps a tamper-evident audit trail.60Apache 2.0
TDQS
Scored across 3 tools
lint_script and check_command_safety overlap substantially because both safety-scan shell content using the same danger engine; their main differentiator is whole-script vs single-command scope, which descriptions do clarify. explain_command is clearly distinct.
All three tools follow a consistent lowercase verb_noun snake_case pattern: lint_script, check_command_safety, explain_command. No mixed conventions or vague placeholder names exist.
Three tools is small but well-scoped for a focused shell safety/explanation utility. Each tool serves a distinct role: whole-script linting, single-command guarding, and command explanation.
For the stated domain of shell command safety, the surface covers the necessary workflows: pre-scanning scripts, checking individual commands before execution, and explaining commands. No obvious dead ends or critical missing operations are apparent.