Skip to main content

Overview

Traceloop Hub includes 12 built-in evaluators organized into three categories. Each evaluator can be configured to run in pre_call mode (on user input), post_call mode (on LLM output), or both depending on your security and quality requirements.

Evaluator Categories

Safety Evaluators (6)

Detect harmful, malicious, or sensitive content to protect users and maintain platform safety.

Validation Evaluators (3)

Ensure data meets format, structure, and syntax requirements.

Quality Evaluators (3)

Assess communication quality, clarity, and confidence.

Quick Reference Table


Safety Evaluators

PII Detector

Evaluator Slug: pii-detector Category: Safety Description: Detects personally identifiable information (PII) such as names, email addresses, phone numbers, social security numbers, addresses, and other sensitive personal data. Uses machine learning models to identify PII with configurable confidence thresholds. Recommended Mode: ✅ Both Post-call and Pre-call Configuration Example:

Secrets Detector

Evaluator Slug: secrets-detector Category: Safety Description: Identifies exposed credentials, API keys, tokens, passwords, and other secrets using pattern matching and entropy analysis. Detects secrets from major providers including AWS, Azure, GitHub, Stripe, OpenAI, and custom patterns. Recommended Mode: ✅ Post-call (primary), Pre-call (secondary) Configuration Example:

Prompt Injection

Evaluator Slug: prompt-injection Category: Safety Description: Detects prompt injection attacks where users attempt to manipulate the LLM by injecting malicious instructions, role-playing commands, jailbreaking attempts, or context overrides. Identifies attempts to bypass system prompts or extract sensitive information. Recommended Mode: ✅ Pre-call only Parameters: Configuration Example:

Profanity Detector

Evaluator Slug: profanity-detector Category: Safety Description: Detects profanity, obscene language, vulgar expressions, and curse words across multiple languages. Useful for maintaining professional communication standards, brand voice, and family-friendly environments. Recommended Mode: ✅ Both (use case dependent) Configuration Example:

Sexism Detector

Evaluator Slug: sexism-detector Category: Safety Description: Identifies sexist language, gender-based discrimination, stereotyping, and biased content. Helps maintain inclusive, respectful communication and comply with diversity and equality standards. Recommended Mode: ✅ Both (highly recommended) Parameters: Configuration Example:

Toxicity Detector

Evaluator Slug: toxicity-detector Category: Safety Description: Detects toxic language including personal attacks, threats, hate speech, mockery, insults, and aggressive communication. Provides granular toxicity scoring across multiple harm categories. Recommended Mode: ✅ Both (essential for safety) Parameters: Configuration Example:

Validation Evaluators

Regex Validator

Evaluator Slug: regex-validator Category: Validation Description: Validates text against custom regular expression patterns. Flexible evaluator for enforcing format requirements, checking for specific patterns, or blocking unwanted content structures. Recommended Mode: ✅ Both (use case dependent) Parameters: Configuration Example:

JSON Validator

Evaluator Slug: json-validator Category: Validation Description: Validates JSON structure and optionally validates against JSON Schema. Ensures LLM-generated JSON is well-formed and meets specific structural requirements. Recommended Mode: ✅ Post-call (primary), Pre-call (secondary) Parameters: Configuration Example:

SQL Validator

Evaluator Slug: sql-validator Category: Validation Description: Validates SQL query syntax without executing the query. Checks for proper SQL structure, detects syntax errors, and ensures query safety. Does not execute queries or connect to databases. Recommended Mode: ✅ Both (use case dependent) Configuration Example:

Quality Evaluators

Tone Detection

Evaluator Slug: tone-detection Category: Quality Description: Analyzes communication tone and emotional sentiment. Identifies whether text is professional, casual, aggressive, empathetic, formal, informal, friendly, or dismissive. Helps maintain consistent brand voice and appropriate communication style. Recommended Mode: ✅ Post-call (primary), Pre-call (secondary) Configuration Example:

Prompt Perplexity

Evaluator Slug: prompt-perplexity Category: Quality Description: Measures the perplexity (predictability/complexity) of prompts. Low perplexity indicates clear, well-formed, coherent prompts. High perplexity may indicate unclear, ambiguous, garbled, or potentially problematic inputs. Recommended Mode: ✅ Pre-call only Configuration Example:

Uncertainty Detector

Evaluator Slug: uncertainty-detector Category: Quality Description: Detects hedging language and uncertainty markers in text such as “maybe”, “possibly”, “I think”, “might”, “could be”, “perhaps”. Useful for identifying when LLM responses lack confidence or are speculative. Recommended Mode: ✅ Post-call only Configuration Example: