Guardrails MCP Server

AI Agent Guardrails MCP server - security layer

Local serverstdio

What is the Guardrails MCP server?

If you already use Guardrails, the guardrails mcp server is the piece that lets your assistant work with it directly. AI Agent Guardrails MCP server - security layer.

What the server does

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.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • validate_input — Validate and sanitize incoming requests through all guardrail checks
  • filter_output — Filter and redact sensitive data (PII, secrets, credentials) from responses
  • check_policy — Evaluate a request against security policies (RBAC, resource access, quotas)
  • get_audit_logs — Query the audit log with filtering by type, user, time range
  • get_stats — Get engine statistics including active users, block rate, request counts
  • update_config — Update guardrail configuration at runtime

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Guardrails's toolset — validate_input, filter_output, check_policy and 3 more — is a fair guide to whether it matches your workflow. It is maintained by ExpertVagabond; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Guardrails's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
validate_inputValidate and sanitize incoming requests through all guardrail checks
filter_outputFilter and redact sensitive data (PII, secrets, credentials) from responses
check_policyEvaluate a request against security policies (RBAC, resource access, quotas)
get_audit_logsQuery the audit log with filtering by type, user, time range
get_statsGet engine statistics including active users, block rate, request counts
update_configUpdate guardrail configuration at runtime

How to install the Guardrails MCP server

## Configuration

```json
{
  "mcpServers": {
    "guardrails": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/guardrails-mcp-server/index.js"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Guardrails to validate input.
  • Use Guardrails to filter output.
  • Use Guardrails to check policy.

Frequently asked questions

It connects Guardrails to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (validate_input, filter_output, check_policy, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Guardrails directly.