Why this server?
Exact match for the searched repository; blocks destructive tool calls like force-push, rm -rf, and secret exfiltration.
Why this server?
Local guardrail proxy that wraps MCP servers and blocks destructive tool calls before execution, with TOFU catalog pinning and injection scanning.
Why this server?
Guardrail sidecar proxy with policy engine, human approval gates, and rate limiting; fail-closed by default.
Why this server?
Runtime safety infrastructure adding budget caps, loop detection, retry limits, and incident reports for agents.
Why this server?
Local-first security gateway enforcing cost caps, blocking prompt injections, and requiring approval for dangerous actions.
Why this server?
Minimal guardrails framework acting as an MCP proxy to enforce policies, approvals, and audit logging.
Why this server?
Guardrails for AI coding agents that enforce rules via compliance receipts and block destructive actions.
Why this server?
Runtime safety guardrails for coding agents; checks file access, validates shell commands, and scores repo AI safety.
Why this server?
Deterministic policy enforcement for agent tool calls, evaluating against user-defined rules before execution.