HabrSeptember 3, 2026🇷🇺Translated from Russian

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

HabrAI Security

Evaluating Jev: Can the New Encoder-Based Model Serve as an Effective Guard for LLMs?

The article examines whether Jev, released by TypeSafe on September 15, can function as a reliable guard model for LLM safety and privacy tasks. It traces the evolution of guard models from early encoder-based solutions like Wildguard to recent LLM-based leaders such as Qwen Guard and YuFeng XGuard. In May 2026, several encoder-based alternatives including gliner guard, gliguard, and gliclass emerged, with Jev standing out due to its unusually large 32K–64K token context window. Benchmark results on NVIDIA’s Aegis 2.0 show Jev achieving an F1 score of 0.85 on prompts and ranking second overall with a score of 0.835, outperforming several LLM-based guards. The model reliably detects jailbreaks, prompt injections, and PII presence but cannot extract specific spans and requires an external API call. Limitations include lack of Russian-language testing and the need for additional NER layers in production.

HabrAI Security

How to Grant AI Agents Access to Internal APIs via MCP: Key Questions Security Teams Will Ask

As AI agents increasingly need to call internal APIs, security teams focus on three core questions: who granted access, how to revoke it, and how to investigate incidents after the fact. The answers lie in operation-level access control rather than traffic inspection alone. MCP, now managed by the Agentic AI Foundation under the Linux Foundation, has become the standard for connecting AI agents to enterprise systems with hundreds of millions of SDK downloads monthly. The article details how NEOMSA APIM implements MCP servers, tool publication from OpenAPI specs, subscription-based scopes, and 15 independent security checks. It explains why classic traffic filters fail against valid but unauthorized tool calls and stresses the need for owner approval, application-specific identities, and proper identity propagation through token exchange. Rate limiting at the subscription level and business-object validation are presented as essential controls to prevent overreach and duplication.

BoletimSecAI Security

HackerSec's Yaga AI Agent Delivers Autonomous Penetration Testing with 98% Effectiveness

HackerSec has developed an autonomous penetration testing platform powered by its Yaga AI agent, marking a shift from scripted automation to adaptive, decision-making offensive security operations. Unlike traditional tools that follow predefined checks, Yaga observes the target environment, interprets responses, forms hypotheses, and replans attack paths in real time while maintaining memory and state across findings. The system relies on a proprietary harness that coordinates advanced AI models, security tools, contextual data, and ongoing decision logic rather than depending on a large language model alone. Yaga already achieves more than 98 percent effectiveness and supports continuous testing that matches the rapid change cycles of modern applications. CEO Andrew Martinez noted that periodic manual pentests can no longer keep pace with AI-accelerated attacks, requiring an AI-native model capable of operating at the same speed as the systems it protects. The platform allows human specialists to monitor and validate results while the agent conducts the investigation independently.

HabrAI Security

AI Gateway Emerges as Unified Control Layer for Enterprise LLM Access and Data Protection

As organizations scale LLM usage beyond individual enthusiasts to dozens of teams, IDEs, internal agents, and automations, AI Gateway becomes essential infrastructure for security, cost management, and reliability. The solution acts as a single entry point that authenticates users, enforces policies, performs DLP checks, depersonalizes sensitive data, routes requests across providers, and enables detailed auditing and billing. Companies face strict requirements under Russian Federal Law 152-FZ on personal data, along with risks of leaks involving API tokens, client information, and internal code when employees bypass official channels. Mature implementations from Cloudflare, Kong, and Microsoft Azure API Management already demonstrate analytics, rate limiting, fallback mechanisms, and governance features. Compatibility with OpenAI API reduces migration friction when switching between providers, including Chinese models, while handling edge cases like tool calls and vision capabilities. The article stresses separating AI Gateway responsibilities from DLP, MCP Gateway, and guardrails to avoid creating an unmanageable monolithic system. Early implementation priorities include ownership, comprehensive auditing from day one, real-world client compatibility testing, shadow-mode DLP, and clear documentation of production architecture.