Agent Guardrail MCP
Related Servers
Alternatives to Agent Guardrail MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseNot gradedqualityFmaintenanceEnables transparent security for any MCP server by intercepting tool calls, blocking prompt injection attempts, masking PII in responses, and writing immutable audit logs.338 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables deterministic detection and neutralization of adversarial prompt injections and override attempts in AI agent workflows via a zero-dependency MCP server, providing structured telemetry and low-latency validation.8-
- AlicenseNot gradedqualityDmaintenanceProvides MCP tools for prompt injection detection and content sanitization, safeguarding LLM pipelines. Also enables Japanese PII scanning and masking for secure data handling.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.64 npm1MIT
- FlicenseNot gradedqualityBmaintenanceProvides 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.-
TDQS
Scored across 4 tools
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.
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.
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.
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.