Specification-based Security Evaluation of Real-World Agents Tool-Calling under Long-Horizon Context Tasks
summary
The gist
The paper introduces RAS-Eval, a comprehensive security benchmark designed to evaluate Large Language Model agents in real-world environments by supporting JSON, LangGraph…
In short
RAS-Eval is a security benchmark for Large Language Model agents, testing their ability to handle tool-calling in real-world settings using JSON, LangGraph, and MCP formats. The benchmark reveals that attacks significantly reduce agent task completion rates by over 36% on average in academic environments.
Key concepts
- RAS-Eval
- A comprehensive security benchmark designed to evaluate LLM agents in dynamic, open, and real-world environments. It supports various tool formats like JSON, LangGraph, and MCP to test agent robustness against attacks.
- Tool Formats
- The benchmark supports three distinct tool formats: JSON for general serialization of test cases and tasks; LangGraph for defining agent workflows; and MCP (Model Context Protocol) scripts tailored for Python-based tools. This allows evaluation across different real-world agent architectures.
- Failure Taxonomy
- A hierarchical classification system that defines six atomic failure modes: F1 through F6. These modes, such as Partial Tool Omission or Null Execution, allow for granular diagnosis of why an agent failed during a security test, helping pinpoint the exact root cause of vulnerabilities.
Terminology used across episodes
This episode discusses
- Specification-based Security Evaluation of Real-World Agents Tool-Calling under Long-Horizon Context Tasks · Paper Radio
- Conversational Health Agents: A Personalized LLM-Powered Agent Framework
- Agent Hospital: A Simulacrum of Hospital with Evolvable Medical Agents
- EHRAgent: Code Empowers Large Language Models for Few-shot Complex Tabular Reasoning on Electronic Health Records
- MAC-SQL: A Multi-Agent Collaborative Framework for Text-to-SQL
- Agent-SafetyBench: Evaluating the Safety of LLM Agents
- Ignore Previous Prompt: Attack Techniques For Language Models
- MCIP: Protecting MCP Safety via Model Contextual Integrity Protocol
- Enterprise-Grade Security for the Model Context Protocol (MCP): Frameworks and Mitigation Strategies
- AIOS: LLM Agent Operating System
- AgentAuditor: Human-Level Safety and Security Evaluation for LLM Agents
- Qwen Technical Report
- LLaMA: Open and Efficient Foundation Language Models
The paper
Specification-based Security Evaluation of Real-World Agents Tool-Calling under Long-Horizon Context Tasks · Read on arXiv
Zhejiang University
Transcript
Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.
Nadia: I'm Nadia.
Elias: And I'm Elias, here with Priya.
Nadia: We're looking at the paper: "Specification-based Security Evaluation of Real-World Agents Tool-Calling under Long-Horizon Context Tasks".
Elias: Here's the gist of the paper. The paper introduces RAS-Eval, a comprehensive security benchmark designed to evaluate Large Language Model agents in real-world environments by supporting JSON, LangGraph, and MCP tool formats The results show that attacks reduced agent task completion rates (TCR) by 36.78% on average and achieved an 85.65% success rate in academic settings Benchmark Construction The dataset is structured into four distinct components: test cases, attack tasks, toolkits, and scenarios The test cases and attack tasks are serialized using JavaScript Object Notation (JSON) format for seamless integration The toolkit encompasses a diverse set of resources including scripts designed to support the LangGraph paradigm, Python scripts tailored for the MCP, and JSON objects To evaluate LLM agents in both real-world and simulated environments, two distinct execution modes were designed for the tools Real Execution involves collecting real-world APIs and MCP-compliant tools from open-source repositories on GitHub Simulated Execution implements simulated tool environments operating on a shared in-memory dictionary object that persists throughout an agent’s task execution Risk Categorization and Failure Taxonomy The risks of all attack tasks and test cases are classified and mapped to the CWE categories The 11 vulnerability types include CWE-77 Command Injection, CWE-89 SQL Injection, and CWE-434 Unrestricted Upload of File with Dangerous Type among others A hierarchical classification system defines six atomic failure modes for granular diagnosis These atomic modes are F1 (Partial Tool Omission), F2 (Sequential Violation), F3 (Null Execution), F4 (Stack Overflow), F5 (Extraneous Invocation), and F6 (Runtime Execution Fault) Compound failures can yield up to 32 different reasons for failure, enabling precise root cause analysis Experimental Validation and Scaling Laws The evaluation utilized eight representative Large Language Models across all test cases, with attack tasks conducted exclusively on the GLM4-Flash model Performance metrics such as Task Completion Rate (TCR), Task Incompletion Rate (TIR), and Task Fail Rate (TFR) were used to evaluate model performance The empirical validation showed that scaling laws hold for security capabilities, with larger models outperforming smaller counterparts For instance, the average attack success rate was 85.65% in academic settings Effectiveness of Attack Tasks The effectiveness of the benchmark's attack tasks was validated by comparing agent performance before and after attacks across various scenarios Table 8 shows that post-attack, average performance scores drop significantly across scenarios, with an average attack success rate of 73.44% This confirms the effectiveness of the benchmark’s attack tasks in evaluating model vulnerabilities The distribution of reasons for task failure shows a difference before and after the attack, indicating vulnerability exposure Discriminative Power and Consistency The benchmark's discriminative power was validated by calculating the Kappa coefficient κ between human and model annotations The average Kappa coefficient of all models is 0.6499, indicating relatively good agreement among the evaluated models Furthermore, the fitting results for the scaling law demonstrated a strong fit with an R2 of 0.9051 This suggests that approximately 90.51% of the variance in performance is explained by the model size In this work, RAS-Eval is proposed as a novel LLM agent security evaluation dataset for dynamic, open, and real-world environments It supports JSON, LangGraph, and MCP tool formats while evaluating agents powered by 7 mainstream LLMs across 7 scenarios The findings offer new ways to design more robust LLM agents REFERENCES
1: Mahyar Abbasian, Iman Azimi, Amir M Rahmani, and Ramesh Jain.
Nadia: Conversational health agents: A personalized llm-powered agent framework.
Elias: arXiv preprint arXiv:2310.02374, 2023.
2: Junkai Li, Yunghwei Lai, Weitao Li, Jingyi Ren, Meng Zhang, Xinhui Kang, Siyu Wang, Peng Li, Ya-Qin Zhang, Weizhi Ma, et al.
Paper summary: Nadia: So to get into this paper "Specification-based Security Evaluation of Real-World Agents Tool-Calling under Long-Horizon Context Tasks," the main thing is that they are addressing the lack of a standard way to evaluate agent security when they are actually using tools in dynamic settings >
Elias: They introduce RAS-Eval, which is this comprehensive security benchmark. It supports JSON, LangGraph, and Model Context Protocol formats for tool execution >
Priya: The thesis of the paper is that you need a benchmark that covers both simulated and real-world tool execution for LLM agents to be truly robust >
Nadia: Right. And they claim this benchmark reveals significant vulnerabilities, showing that attacks can reduce agent task completion rates by thirty-six point seventy-eight percent on average in academic settings > <ref:2506.15253#pg1>
Elias: They also show an eighty-five point sixty five percent success rate for those attacks in academic settings, which is the main result they highlight about the vulnerability exposure >
Priya: It matters because it gives us a structured way to see these vulnerabilities mapped to eleven Common Weakness Enumeration categories and defines six atomic failure modes for diagnosis >
Nadia: That structure helps researchers actually pinpoint where the agent is failing, which is much better than just getting a vague failure report >
Elias: And they also show that scaling laws hold for security capabilities. This means bigger models tend to be more secure when evaluating these agent tool-calling scenarios, according to the paper "Specification-based Security Evaluation of Real-World Agents Tool-Calling under Long-Horizon Context Tasks"
Priya: So, in short, it’s about creating a benchmark that tests real agent behavior against specific attack types and shows that model size affects security performance >
Nadia: It really matters because it gives us a tool to design more robust agents for critical domains like healthcare or finance without just guessing at where the weak points are >
Elias: So, they’re providing a comprehensive dataset that allows people to test these agents in diverse, real-world scenarios and understand the security landscape of agent tool usage >
Conclusion: Nadia: Thinking about the title, "Specification-based Security Evaluation of Real-World Agents Tool-Calling under Long-Horizon Context Tasks," it really boils down to testing agents when they are actually using tools over long periods >
Elias: That’s right. It’s not just a quick check; it involves checking tool calling, context length, and the environment they're operating in >
Priya: What this implies is that for any agent deployment, you need to consider the full lifecycle of its tasks and how those tools interact over time >
Nadia: And the authors are providing this RAS-Eval benchmark as a way to make that consideration concrete for practitioners, giving them something tangible to work with >
Elias: It’s about moving from theoretical concerns about agent security to practical evaluation, using things like JSON and MCP formats that are actually used in development today >
Priya: So the implication is that we need standardized testing protocols for these agents so we can build trust in them when they're making decisions based on external tools >
Nadia: Exactly. It gives us a common language to discuss vulnerabilities, which helps everyone—the developers and the security researchers—understand each other better >
Elias: So this paper is about establishing a formal way to benchmark the security of LLM agents in these specific, long-horizon contexts, providing a foundation for future research on agent safety >
More episodes
- 2608.27496-ROPE: Routed Origin Policy Enforcement against Indirect Prompt Injection
- Daily Summary for 2026-11-19
- 2607.07085-Is Randomness Necessary for Adaptive Data Analysis?
- The day in conversation for 2026-11-19
- Daily Summary for 2026-11-19
- 2609.10601-Threshold Choice, Not Sample Size, Bounds Trustless Verification of Nondeterministic Compound AI Workflows
- 2610.38786-Adversarial Process Disturbances at a Deployable Alarm Budget: Detector Evaluation on a Simulator and a Real Plant
- 2511.08660-Binary and Multiclass Cyberattack Classification on GeNIS Dataset
- 2604.27302-Static Attribution of Android Residential Proxy Malware Using Graph Kernels
- Daily Summary for 2026-11-18