Skip to main content
Content‑security detectors are the LLM‑aware core of TrustGuard: they score prompts and model output for jailbreaks, toxicity, and off‑topic/disallowed content, and analyze documents and URLs. Several call the NeuralTrust Firewall; its credentials are configured globally (env) or overridden per‑detector under settings.credentials. All of these are detection‑only — the action (Monitor / Block) and evaluation phase (Input / Output) are set on the policy rule that references the detector.

Prompt Guard — prompt_guard

Scores input/output with the NeuralTrust Firewall jailbreak detector and reports a finding (signal.type: "jailbreak") above a threshold.
Detector Sensitivity in the console uses three levels for all detectors: Permissive, Balanced (recommended), and Strict. The API jailbreak.threshold (and similar threshold fields) maps to the same sensitivity knob for automation — prefer the console Sensitivity control when configuring from the UI.

Toxicity — toxicity

Scores content with the NeuralTrust Firewall toxicity detector and reports a finding above threshold. The signal.type is the firewall category that scored highest (e.g. hate, violence, harassment, self_harm, sexual).

Moderation — prompt_moderation

Dual‑mode moderation — enable at least one mode.

URL Analyzer — url_analyzer

Extracts URLs from content, fetches each page (SSRF‑guarded, size/timeout‑bounded, up to 10 URLs per request), and screens the fetched text for jailbreaks and PII.

Document Analyzer — doc_analyzer

Extracts text from uploaded documents (PDF, Office, images via OCR, plain text) sent as payload.attachments, then screens for PII and (optionally) jailbreaks.

When to use

  • prompt_guard is the baseline jailbreak defense for chat traffic.
  • url_analyzer / doc_analyzer for RAG and agent flows that ingest links/files.
  • toxicity on input and/or output for abuse and safety.
  • prompt_moderation for topic/scope control (“only answer about X”).