NeuralTrust | Platform for Agent Security.

Beyond routing and cost controls, TrustGate ships guardrail policies that inspect request and/or response content and block (or transform) what they flag. Attach one — or several — as a policy, global or per consumer.

Configure in the console

Open Policies → Catalog (guardrails are listed first).
Pick TrustGuard (recommended), OpenAI Moderation, Azure Content Safety, Bedrock Guardrail, or Regex Replace.
For TrustGuard, select or create an Agent Runtime collector when prompted — connection settings are platform-managed on SaaS.
Set direction (request / response), mode (Enforce / Observe), and scope.
Save. Exercise blocks in the Playground; inspect Security flags under Activity.

Policy (`slug`)	Provider	Stages
`trustguard`	NeuralTrust TrustGuard	`pre_request` · `pre_response`
`openai_moderation`	OpenAI Moderations API	`pre_request` · `pre_response`
`azure_content_safety`	Azure AI Content Safety	`pre_request`
`bedrock_guardrail`	AWS Bedrock Guardrails	`pre_request` · `pre_response`
`regex_replace`	Built-in RE2 rewrite	`pre_request` or `pre_response`

Streaming responses cannot be inspected or blocked in realtime by these policies. Apply guardrails on the request leg (or to non-streaming responses) for enforcement.

TrustGuard

The trustguard policy inspects content with TrustGuard — NeuralTrust’s runtime security service for jailbreaks, PII, toxicity, and tool abuse — and block what it flags. This is the deepest detection option and the recommended default for NeuralTrust deployments.

Setting	Type	Default	Notes
`collector_id`	string	—	TrustGuard collector UUID bound to this policy. Required.
`direction`	enum	`request`	`request`, `response`, or `request_response`.

TrustGuard fails open: on any transport error, timeout, non-2xx response, or missing base URL, the request passes through. Connection settings come from the deployment’s TRUSTGUARD_* environment. See the TrustGate integration.

{ "slug": "trustguard", "settings": { "collector_id": "<uuid>", "direction": "request_response" } }

OpenAI Moderation

The openai_moderation policy screens text with the OpenAI Moderations API and blocks content that crosses configured category thresholds. Text-only.

Setting	Type	Default	Notes
`api_key`	string	—	OpenAI credential (Bearer). Required.
`model`	string	`omni-moderation-latest`	Moderations model.
`stages`	enum[]	—	Legs to inspect: `pre_request`, `pre_response`.
`categories`	string[]	—	Categories to evaluate (empty = all returned).
`thresholds`	map	—	Per-category score threshold `0..1`; a score ≥ threshold blocks.
`block_on_flagged`	bool	`false`	Block anything OpenAI marks flagged, even without a threshold.
`action.message`	string	—	Block message returned to the caller.

In enforce mode this policy fails closed (HTTP 502) on any moderator error; observe mode records and passes through.

{
  "slug": "openai_moderation",
  "settings": {
    "api_key": "sk-…",
    "stages": ["pre_request"],
    "thresholds": { "harassment": 0.7, "hate": 0.5 },
    "block_on_flagged": true
  }
}

Azure Content Safety

The azure_content_safety policy screens request content with the Azure AI Content Safety Analyze Text API and blocks categories whose severity meets the configured threshold.

Setting	Type	Default	Notes
`api_key`	string	—	Azure subscription key (`Ocp-Apim-Subscription-Key`). Required.
`endpoint`	string	—	Absolute Analyze Text endpoint URL. Required.
`output_type`	enum	`FourSeverityLevels`	`FourSeverityLevels` (0/2/4/6) or `EightSeverityLevels` (0–7).
`categories`	enum[]	all	`Hate`, `Violence`, `SelfHarm`, `Sexual`.
`category_severity`	map	—	Per-category severity threshold; only listed categories are enforced. Required.
`message`	string	—	Optional block message.

Fails closed in enforce mode.

{
  "slug": "azure_content_safety",
  "settings": {
    "api_key": "…",
    "endpoint": "https://<resource>.cognitiveservices.azure.com/contentsafety/text:analyze?api-version=2024-09-01",
    "category_severity": { "Hate": 4, "Violence": 4 }
  }
}

AWS Bedrock guardrail

The bedrock_guardrail policy applies an AWS Bedrock guardrail to request prompts and/or responses. It inspects the topic, content, word, sensitive-information (PII), and contextual-grounding policy families configured on the guardrail, and blocks with a 403 or anonymizes PII in place. Streaming responses pass through untouched.

Setting	Type	Default	Notes
`guardrail_id`	string	—	AWS Bedrock guardrail identifier. Required.
`version`	string	`DRAFT`	Guardrail version.
`pii_action`	enum	`block`	On sensitive-info match: `block` or `anonymize`.
`message`	string	—	Optional block message.
`credentials`	object	—	AWS auth (region, static keys or `use_role` + `role_arn`). Required.

{
  "slug": "bedrock_guardrail",
  "settings": {
    "guardrail_id": "abcd1234",
    "version": "DRAFT",
    "pii_action": "anonymize",
    "credentials": { "aws_region": "us-east-1", "use_role": true, "role_arn": "arn:aws:iam::…:role/…" }
  }
}

Regex Replace

The regex_replace policy (Regex Replace in the catalog) rewrites the request prompt or the LLM response with ordered RE2 regular expressions. Rules chain: each rule sees the previous rule’s output. A single policy instance targets one leg (request or response), not both. Streaming responses pass through untouched.

Configure in the console

Policies → Catalog → Regex Replace.
Choose the target leg (request or response) and add ordered rewrite rules (pattern, replacement, optional case-insensitive / multiline).
Set mode and scope, then save.

Setting	Type	Default	Notes
`target`	enum	—	`request` or `response`. Required.
`rules`	array	—	Ordered `[{ pattern, replacement, case_insensitive, multiline }]`. Required.
`rules[].pattern`	string	—	RE2 pattern (no backreferences or lookaround). Required.
`rules[].replacement`	string	—	Replacement text; `$1` / `${name}` for capture groups. Empty removes the match.
`rules[].case_insensitive`	bool	`false`	Match without regard to letter case (`(?i)`).
`rules[].multiline`	bool	`false`	`^` and `$` match at line boundaries (`(?m)`).

{
  "slug": "regex_replace",
  "settings": {
    "target": "request",
    "rules": [
      { "pattern": "\\b(ssn|social)\\b", "replacement": "[REDACTED]", "case_insensitive": true }
    ]
  }
}

Choosing a guardrail

trustguard — the richest, NeuralTrust-native detection; use it as the primary guardrail and correlate its findings with Telemetry Alerts.
openai_moderation / azure_content_safety — lightweight content moderation if you already use those providers.
bedrock_guardrail — reuse guardrails you’ve already defined in AWS Bedrock, including in-place PII anonymization.
regex_replace — deterministic string rewrite when you need simple pattern-based redaction or rewriting without an external moderator.

Guardrails compose: run several in one policy chain (e.g. TrustGuard on the request plus a Bedrock guardrail for PII anonymization on the response).

Introduction

Getting started

Console

Core concepts

Routing

Policies

MCP

Observability

Operate

Admin API

API reference

Guardrails

Configure in the console

TrustGuard

OpenAI Moderation

Azure Content Safety

AWS Bedrock guardrail

Regex Replace

Configure in the console

Choosing a guardrail

​Configure in the console

​TrustGuard

​OpenAI Moderation

​Azure Content Safety

​AWS Bedrock guardrail

​Regex Replace

​Configure in the console

​Choosing a guardrail

Configure in the console

TrustGuard

OpenAI Moderation

Azure Content Safety

AWS Bedrock guardrail

Regex Replace

Configure in the console

Choosing a guardrail