Paper

{
  "raw_xml": "<entry>\n    <id>http://arxiv.org/abs/2603.15408v1</id>\n    <title>TrinityGuard: A Unified Framework for Safeguarding Multi-Agent Systems</title>\n    <updated>2026-03-16T15:20:38Z</updated>\n    <link href='https://arxiv.org/abs/2603.15408v1' rel='alternate' type='text/html'/>\n    <link href='https://arxiv.org/pdf/2603.15408v1' rel='related' title='pdf' type='application/pdf'/>\n    <summary>With the rapid development of LLM-based multi-agent systems (MAS), their significant safety and security concerns have emerged, which introduce novel risks going beyond single agents or LLMs. Despite attempts to address these issues, the existing literature lacks a cohesive safeguarding system specialized for MAS risks. In this work, we introduce TrinityGuard, a comprehensive safety evaluation and monitoring framework for LLM-based MAS, grounded in the OWASP standards. Specifically, TrinityGuard encompasses a three-tier fine-grained risk taxonomy that identifies 20 risk types, covering single-agent vulnerabilities, inter-agent communication threats, and system-level emergent hazards. Designed for scalability across various MAS structures and platforms, TrinityGuard is organized in a trinity manner, involving an MAS abstraction layer that can be adapted to any MAS structures, an evaluation layer containing risk-specific test modules, alongside runtime monitor agents coordinated by a unified LLM Judge Factory. During Evaluation, TrinityGuard executes curated attack probes to generate detailed vulnerability reports for each risk type, where monitor agents analyze structured execution traces and issue real-time alerts, enabling both pre-development evaluation and runtime monitoring. We further formalize these safety metrics and present detailed case studies across various representative MAS examples, showcasing the versatility and reliability of TrinityGuard. Overall, TrinityGuard acts as a comprehensive framework for evaluating and monitoring various risks in MAS, paving the way for further research into their safety and security.</summary>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.CR'/>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.AI'/>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.CL'/>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.LG'/>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.MA'/>\n    <published>2026-03-16T15:20:38Z</published>\n    <arxiv:primary_category term='cs.CR'/>\n    <author>\n      <name>Kai Wang</name>\n    </author>\n    <author>\n      <name>Biaojie Zeng</name>\n    </author>\n    <author>\n      <name>Zeming Wei</name>\n    </author>\n    <author>\n      <name>Chang Jin</name>\n    </author>\n    <author>\n      <name>Hefeng Zhou</name>\n    </author>\n    <author>\n      <name>Xiangtian Li</name>\n    </author>\n    <author>\n      <name>Chao Yang</name>\n    </author>\n    <author>\n      <name>Jingjing Qu</name>\n    </author>\n    <author>\n      <name>Xingcheng Xu</name>\n    </author>\n    <author>\n      <name>Xia Hu</name>\n    </author>\n  </entry>"
}