Raft Develops Multilabel Guardrail Classifier Detecting 15 Risk Categories with 3x Speed and Cost Gains
Raft has published a detailed technical account of how it built and production-optimized a multilabel guardrail classifier capable of simultaneously evaluating 15 risk categories on both user prompts and model generations.
The classifier addresses regulatory, reputational and operational risks that arise when generative systems produce or receive disallowed content such as child exploitation material, violent crime instructions, weapons, narcotics, self-harm, discrimination, Nazism, financial crime, cybercrime and adult content, as well as thematic categories including profanity, religious offences and LGBT-related material governed by specific Russian legislation.
Unlike binary toxicity detectors or keyword filters, the model outputs 15 independent probability scores, each with its own calibrated threshold. Deploying organisations can therefore enable or disable any subset of categories without retraining.
Performance and Economics
On an NVIDIA RTX 3090, the TensorRT backend delivered 5.9 ms P95 latency for batch-1 requests compared with 17.4 ms for the PyTorch + FlashAttention2 baseline, a 2.95× improvement. At the optimal batch size of 16, throughput reached 1 345 texts per second and cost fell to $0.062 per million requests, 2.9× cheaper than a naïve PyTorch batch-8 configuration.
The model was trained with asymmetric loss to prioritise recall on rare but critical classes and uses a two-layer transformer to model statistical dependencies between categories such as armament and violent actions.
Benchmark Results
In a balanced evaluation of 7 480 examples, HiveTrace Multilabel achieved binary F1 of 0.9588 and macro-F1 of 0.7026 across 14 labels, outperforming Qwen3Guard variants and other open toxicity models on the macro metric that better reflects per-category utility for real moderation workflows.
A second open model, gliner_guard_omni, was also released by the team. Both models are positioned as fast, on-premise ML filters that sit between regex checks and slower external LLM judges in production guardrail pipelines.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.