runtime-guard-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNTIME_GUARD_CONFIG | No | Path to the configuration file (see runtime-guard.example.json). | |
| RUNTIME_GUARD_AUTH_TOKEN | No | Required for non-loopback binding of the HTTP transport. | |
| RUNTIME_GUARD_WORKSPACE_ROOT | Yes | Set to the intended workspace root for the local stdio server (e.g., `$PWD`). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_path_accessB | Advisory path containment check; follows existing symlinks but does not authorize a later filesystem operation. |
| dry_run_commandA | Classify shell text without executing it. SAFE is heuristic, not permission to execute. |
| budget_guardC | Check or atomically consume caller-wide token, payload, and command budgets; detects repeated session actions. |
| secret_maskerB | Mask common credentials in output chunks using stable placeholders within a caller; final=true flushes buffered text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.