Skip to main content
Glama
pgguard-mcp

pgguard-mcp

by Azzaraell

Related Servers

Alternatives to pgguard-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only PostgreSQL interaction with enforced SQL security policies, including query validation, row limits, and timeouts.
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents read-only access to Postgres with parser-checked queries, hidden tables and columns, row limits and timeouts, caller-bound Row-Level Security, and a tamper-evident audit log.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to PostgreSQL databases via MCP, enforcing least-privilege roles, row-level security, masked views, and SQL AST guardrails to prevent data leakage and unauthorized operations, enabling AI agents to safely query sensitive production data.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query a Postgres data warehouse through a governed, read-only SQL interface with policy enforcement, row limits, schema-level PII isolation, and a full audit trail.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query a Postgres database read-only through a policy layer rather than a raw connection string. Enforces table and column allowlists, row limits, mandatory predicates, PII masking and append-only audit logging, while refusing writes, joins, subqueries and unlisted functions.
      MIT

    TDQS

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: policy overview, table listing, table details, row sampling, arbitrary queries, and query planning. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., describe_access, list_tables, run_query), making them predictable and easy to understand.

    Tool Count5/5

    With 6 tools, the set is well-scoped for the domain of policy-enforced database querying, covering introspection, sampling, and full querying without being bloated.

    Completeness5/5

    The tools cover the full lifecycle of interacting with the access policy: understanding the policy, listing/detailing tables, sampling data, running arbitrary queries, and explaining plans. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues