Skip to main content
Glama
ss-2303

Agent Guardrail MCP

by ss-2303

Related Servers

Alternatives to Agent Guardrail MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to enforce security policies by authorizing tool calls, scanning for prompt injection, checking memory writes, redacting PII, and accessing audit trails through MCP.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP tools for prompt injection detection and content sanitization, safeguarding LLM pipelines. Also enables Japanese PII scanning and masking for secure data handling.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.
      42 npm
      1
      MIT
    • 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
      B
      maintenance
      Security middleware for LLM agents. Authorize tool calls, scan for injection, quarantine poisoned memory, and redact PII — all through MCP. 0% injection success rate on 1,054 tested attacks.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a governance gateway for LLM and agent traffic via MCP, blocking prompt injection, redacting PII, enforcing per-tenant token budgets, and caching repeat questions semantically. Enables AI agents to route model calls through the same guardrails instead of calling providers directly.
      MIT

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: scanning input for injection, scanning output for PII/secrets, retrieving detailed audit entries, and getting aggregate statistics. No overlap or potential confusion.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: get_audit_trail, get_guardrail_stats, scan_input, scan_output. The naming is predictable and intuitive.

    Tool Count5/5

    With only 4 tools, the set is well-scoped for a guardrail system that scans inputs and outputs, provides an audit log, and offers aggregate statistics. Each tool serves a clear, non-redundant function.

    Completeness5/5

    The tool surface covers the core lifecycle: scanning input (injection detection), scanning output (PII/secrets), reviewing history via audit trail, and obtaining overview stats. No obvious gaps for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues