Skip to main content
Glama
LOLA0786

privatevault-gate

by LOLA0786

Related Servers

Alternatives to privatevault-gate

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gates every AI agent tool call against your policy before it runs, then writes a hash-chained, tamper-evident record of what was decided and what happened. Anyone can verify that record offline, without your software, your systems or any key you hold.
      1,766 PyPI
      15
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Policy gateway for AI agent tool calls: checks every MCP, shell and file call against one provio.yaml (allow / deny / ask / redact) before it runs, pins MCP tool definitions against rug pulls, and records each decision in a tamper-evident, signed ledger.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables governed tool-calling agents with policy decisions, optional human approval, hash-chained audit logging, and deterministic evaluation.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to safely invoke enterprise MCP tools under an enforceable guard that applies allowlist policies, caller roles, parameter restrictions, human confirmation for destructive operations, and a correlated JSONL audit log.
      AGPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to call external endpoints under per-endpoint policy enforcement, with credentials and personal data kept inside a hardware enclave and every allowed or denied attempt recorded to an immutable audit ledger.
      2
      -

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each pv_* tool has a distinct purpose (exec, write, HTTP, decide, list blocked). Minimal ambiguity between pv_decide (advisory) and the gated tools is mitigated by clear descriptions of enforcement.

    Naming Consistency4/5

    All tools use a consistent pv_ prefix with snake_case verbs. Minor deviation: 'decide' is an action but 'blocked' is a list operation, but the pattern is still predictable.

    Tool Count5/5

    Five tools perfectly suit a security-gating server: core gated operations plus an advisory decision and a history check. No bloat or gap in scope.

    Completeness4/5

    The server covers the essential lifecycle of gating actions and checking decisions. Missing features like allowing/denying decisions or a detailed audit log, but these are secondary for advisory/lists.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues