WhitePact
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAI_API_KEY | Yes | Bearer token for authenticating with the WhitePact REST API | |
| RAI_API_URL | Yes | The URL of the WhitePact REST API (e.g., http://localhost:8765) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rai_scanA | Scan text for PII (email, phone, SSN, credit card, IP address) and harmful content (hate speech, violence, self-harm). Returns findings and a redacted copy. |
| rai_trust_scoreB | Compute a composite AI Trust Score (0-100) across six governance dimensions: fairness, privacy, security, robustness, compliance, authenticity. Returns score, letter grade (A-F), and risk tier (LOW/MEDIUM/HIGH/CRITICAL). |
| rai_complianceA | Evaluate AI governance maturity against NIST AI RMF, EU AI Act, or ISO 42001, given your own self-assessed control scores (fairness/privacy/security/robustness 0-1, plus overall compliance maturity 0-1). Returns a compliance score, findings per control, and remediation recommendations. Use this when the caller already has maturity/control scores and wants a gap assessment. Do NOT use this to classify what EU AI Act risk tier a specific system falls into from a description of what it does (sector, automation, biometric use, etc.) -- use |
| rai_hallucinationA | Detect hallucination risk in AI-generated text. Analyses hedging language, self-consistency across candidate responses, unsupported factual claims, and (when a |
| rai_cost_estimateC | Estimate the USD cost of a model API call from token counts. |
| rai_redteam_payloadsA | Return adversarial attack payloads to probe an AI model for security vulnerabilities. Categories: prompt_injection, jailbreak, data_leakage, role_confusion, delimiter_attack. |
| rai_redteam_analyzeB | Analyse model responses to red team attack payloads. Returns a security report with vulnerability findings, severity breakdown, and an overall security score. |
| rai_compare_modelsB | Compare two AI models across all six trust dimensions. Returns scores for each, delta analysis, and a recommendation on which model is more trustworthy. |
| rai_audit_summaryA | Return a governance capability summary including supported tools, frameworks, and available attack vectors. Full audit log access requires the REST endpoint. |
| rai_healthB | Check the status and module availability of the ResponsibleAI governance engine. |
| rai_bias_evaluateA | Evaluate demographic bias across six probe dimensions: gender, racial, age, religious, occupational, and cultural. Provide paired response samples for each demographic group. Returns per-probe bias scores (0=no bias, 1=maximum divergence), confidence intervals, intersectional amplification, and an overall bias grade. |
| rai_drift_checkA | Detect trust score drift between a baseline evaluation and a current evaluation. Returns drift delta per dimension, overall drift severity (NONE/LOW/MEDIUM/HIGH/CRITICAL), and whether an alert threshold was breached. |
| rai_passport_generateB | Generate a verifiable AI Passport for a model — a tamper-evident governance card containing trust scores, compliance status, bias summary, and a cryptographic verification hash. Used by Procurement/Legal for third-party AI vendor risk assessment. |
| rai_budget_checkB | Evaluate current AI spending against monthly budget limits. Returns consumption percentage, alert status, per-team and per-model breakdown, and projected month-end spend. Used by LLMOps Engineers and Finance to prevent budget overruns. |
| rai_policy_checkA | Evaluate text or a model response against a governance policy. Checks for: prohibited topics, required disclaimers, output length limits, language restrictions, and custom keyword blocklist. Returns pass/fail per policy rule with remediation guidance. |
| rai_stream_scanA | Scan a list of text chunks (as would arrive from an LLM streaming response) for PII and harmful content. Simulates the StreamingScanner guardrail without a live stream. Returns per-chunk scan results and an aggregated summary with stop recommendation. |
| rai_benchmarkA | Evaluate pre-collected model responses against a standard benchmark suite. Suites: truthfulqa (factual accuracy), bbq (bias in questions), hellaswag (reasoning). Call rai_benchmark_prompts first to get the question set, collect responses, then pass them here. |
| rai_benchmark_promptsA | Return the question set for a benchmark suite. Use to collect model responses before calling rai_benchmark. Suites: truthfulqa, bbq, hellaswag. |
| rai_model_routeA | Recommend the optimal AI model for a task based on complexity analysis and cost-quality tradeoff. Returns recommended model, alternative, estimated cost per 1K tokens, and estimated savings vs GPT-4o. Used by LLMOps Engineers for intelligent model routing. |
| rai_pii_reportA | Generate a detailed PII audit report for a document or corpus. Classifies findings by PII category (email, phone, SSN, credit card, IP, address), counts occurrences, computes a privacy risk score, and provides GDPR/CCPA remediation guidance. Used by Privacy Engineers for compliance evidence collection. |
| rai_incident_logC | Create a structured governance incident record. Used by Security Engineers and AI Risk Analysts to log AI safety events (PII leaks, jailbreak attempts, bias triggers, hallucination incidents) for audit trail and SIEM integration. |
| rai_eu_ai_act_classifyA | Classify an AI system into an EU AI Act risk tier: UNACCEPTABLE, HIGH, LIMITED, or MINIMAL, from a description of what the system does (deployment sector, automation level, biometric/emotion-recognition use). Evaluates deployment context, capabilities, and affected populations against Annex III and Annex VI criteria. Returns risk tier, applicable articles, required conformity assessment actions, and a compliance roadmap. Use this for 'what EU AI Act category does this system fall into' questions. Do NOT use this for a general maturity/gap assessment against self-scored controls (fairness/privacy/security scores) -- use |
| rai_iso42001_gapC | Perform an ISO/IEC 42001:2023 AI Management System gap analysis. Evaluates maturity across all 10 clauses: Context, Leadership, Planning, Support, Operation, Performance Evaluation, Improvement, plus AI-specific annexes. Returns gap findings, maturity scores per clause, and a prioritised remediation roadmap. Used by AI Compliance Managers. |
| rai_executive_summaryA | Generate a board-ready executive AI governance summary. Synthesises trust grades, compliance posture, cost intelligence, risk incidents, and drift trends into a C-suite-readable report with RAG (Red/Amber/Green) status indicators. Used by CAIO for quarterly board reporting. |
| rai_org_statusA | Compute a structured governance status rollup. The health/grade/compliance fields (models, compliance, operations) are always derived FROM caller-supplied metrics (model grades, active frameworks, open incidents, budget usage, drift alerts) -- there is no separate store of these tracked per-org yet, so calling with none supplied rolls up empty/default values, not fabricated data. The org_id/plan/usage fields are different: on the hosted MCP transport with an authenticated caller, these reflect the real, live org record and this month's real call count against quota -- absent (not present in the response at all) on the self-hosted stdio transport, where there is no org account to look up. |
| rai_check_trustA | Check the public, independently-verifiable Trust Index score, certification status, and reported-incident history for a named AI model or tool BEFORE invoking it. Unlike every other rai_* tool, which evaluates output the caller itself produced, this one looks up a public record about a THIRD PARTY'S model or tool — built for agents and agent frameworks (LangChain, LangGraph, Google ADK) deciding whether to trust something before calling it. Free, no auth required, exact model+provider match. Queries the hosted ResponsibleAI Trust Index (configurable via the RAI_TRUST_API_BASE environment variable). Returns 'known: false' for anything never assessed — that is not an error, just an absence of data; self-assessment is free at POST /api/trust-index/assess. |
| rai_webhook_statusB | Check webhook delivery health and generate a structured status report. Takes delivery statistics and returns health grade, failure analysis, dead-letter queue status, and recommended remediation actions. Used by Security Engineers feeding SIEM systems and Platform Engineers debugging webhook pipelines. |
| rai_memory_write_checkA | Gate a write to PERSISTENT agent memory (a vector DB, conversation log, or similar long-term store your own system owns -- WhitePact does not host a memory store itself). Scans the content for prompt-injection patterns aimed specifically at persistent memory -- text engineered to look like an instruction, a fake system/assistant role marker, or an override, so that a future session reading this memory back treats it as trusted context rather than as content. Call this BEFORE actually persisting the write; if 'allowed' is false, do not write it. When governance is enabled on the hosted MCP server and the caller's authority carries a memory_scope constraint, memory_scope is also checked for cross-tenant/cross-agent isolation -- outside the governed dispatch path this tool only runs the content scan. |
| rai_memory_read_checkA | Gate a read from persistent agent memory. Standalone, this tool only echoes back the requested scope (there's no content to scan for a read) -- its real enforcement value is when governance is enabled on the hosted MCP server: the caller's authority's memory_scope constraint (if any) is checked against the requested memory_scope, denying cross-tenant/cross-agent memory access before the read happens. |
| rai_causal_influence_checkA | Scan a list of upstream sources that causally shaped a proposed action (a prior tool's output, a sub-agent's result, an external document, ...) for prompt-injection patterns, and flag whether any of them are untrusted. Generalizes rai_memory_write_check beyond persistent memory: any content that will be treated as trusted context by whatever consumes this action's result carries the same replay risk memory does. Each provenance entry needs a 'kind' (memory_read | tool_output | sub_agent_result | user_input | external_content) and a 'trust' level (TRUSTED | UNTRUSTED | UNKNOWN); 'content' is optional (an entry may assert only its trust level with nothing to scan). Call this before letting a matched/untrusted source influence a real action -- when governance is enabled on the hosted MCP server, the same check also runs automatically on any governed action whose arguments carry a '_provenance' key in this same shape. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ResponsibleAI Health | Current health status of the ResponsibleAI governance service |
| Model Pricing Catalog | Supported AI models with per-token pricing for cost estimation |
| Compliance Frameworks | Supported AI governance frameworks: NIST AI RMF, EU AI Act, ISO 42001 |
| Red Team Attack Categories | Adversarial attack categories used in automated security probing |
| Trust Score Dimensions | Six governance dimensions used to compute the composite AI Trust Score |
| Bias Probe Catalog | Available demographic bias probes, methodology, and scoring interpretation |
| Governance Policy Template | Default governance policy template with configurable rules for rai_policy_check |
| Trust Grade Reference | Trust score grade thresholds, risk tier mapping, and deployment guidance |
| NIST AI RMF Checklist | Actionable NIST AI Risk Management Framework implementation checklist |
| EU AI Act Compliance Checklist | EU AI Act compliance checklist for high-risk AI system operators |
| ResponsibleAI Health | Current health status of the ResponsibleAI governance service |
| Model Pricing Catalog | Supported AI models with per-token pricing for cost estimation |
| Compliance Frameworks | Supported AI governance frameworks: NIST AI RMF, EU AI Act, ISO 42001 |
| Red Team Attack Categories | Adversarial attack categories used in automated security probing |
| Trust Score Dimensions | Six governance dimensions used to compute the composite AI Trust Score |
| Bias Probe Catalog | Available demographic bias probes, methodology, and scoring interpretation |
| Governance Policy Template | Default governance policy template with configurable rules for rai_policy_check |
| Trust Grade Reference | Trust score grade thresholds, risk tier mapping, and deployment guidance |
| NIST AI RMF Checklist | Actionable NIST AI Risk Management Framework implementation checklist |
| EU AI Act Compliance Checklist | EU AI Act compliance checklist for high-risk AI system operators |
TDQS
Scored across 30 tools
Despite covering overlapping governance themes, descriptions carry explicit 'use X instead of Y' guidance (e.g., rai_compliance vs rai_eu_ai_act_classify, rai_trust_score vs rai_check_trust), and the scan-family (rai_scan/rai_stream_scan/rai_pii_report) and memory-family tools are clearly differentiated. Each tool has a distinct resource+action target with no true duplicates.
Every tool uses a uniform rai_ prefix with a consistent snake_case convention (rai_trust_score, rai_policy_check, rai_bias_evaluate). No mixing of camelCase, no erratic verb styles.
30 tools is heavy and pushes past the comfortable ceiling, even if the governance domain is genuinely broad (privacy, security, compliance, cost, bias, audit). Most tools earn their place, but a set this large increases selection burden for agents.
The surface covers an unusually full governance lifecycle: scanning, trust scoring, bias evaluation, compliance (NIST/EU AI Act/ISO 42001), red-teaming, cost/budget, drift, passports, incident logging, and memory/provenance gating. No obvious dead ends for the stated purpose.