runtime-guard-mcp
Related Servers
Alternatives to runtime-guard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceSafety checks an agent runs before it acts — flags malicious packages, destructive shell commands, secret leaks, and web-backend holes before execution.828 PyPIMIT
- FlicenseAqualityBmaintenanceEnables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.143-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables autonomous agents to run shell and subprocess commands through a guardrail that blocks destructive system mutations, path traversals, and reverse shells. It also adds prompt-injection detection, spend circuit breakers, loop detection, and privacy sanitization so agent execution stays within safe, budgeted bounds.MIT
- AlicenseNot gradedqualityBmaintenanceEnables autonomous agents to enforce financial guardrails by tracking real-time token burn and cost velocity, automatically throttling or freezing execution when budgets are exceeded. It also blocks destructive shell commands, prompt injections, and runaway planning loops while sanitizing outputs before they are returned.7MIT
- 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.6173 npm5Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables autonomous coding agents to run deterministic pre-flight static checks on diffs and repositories, export SARIF findings, execute commands with HMAC-SHA256 signed receipts, verify receipt integrity, enforce output constraints, and synchronize safety rules across agent configs.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct guard domain: path containment, shell command classification, budget consumption, and secret redaction. No overlapping purposes; an agent can easily choose the right tool based on input type.
All names use snake_case and are descriptive, but the pattern mixes action-oriented (audit_path_access, dry_run_command) and agent/noun-oriented (budget_guard, secret_masker) forms. Minor deviation from a single verb_noun convention, yet still readable.
Four tools is well within the typical 3–15 range and each covers a separate guard function. No tool feels redundant or missing for the core scope.
Covers common runtime guardrails: path access, command execution, budgets, and secrets. Minor gaps exist such as network egress validation or non-secret content checks, but core workflows are covered.