Human Feedback Types
missingNone explicit
No explicit feedback protocol extracted.
"Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them."
HFEPX · Eval paper review
Yicheng Cai, Taegyu Kim, Peng Liu
Published
Nov 19, 2026
Citations
0
Trust level
Low
Usefulness score
0/100 (Low)
Extraction confidence
15% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Nov 19, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
All signals on this page are inferred from the abstract only and may be inaccurate. Do not use this page as a primary protocol reference.
Best use
Background context only
Use if you need
A secondary eval reference to pair with stronger protocol papers.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
This paper looks adjacent to evaluation work, but not like a strong protocol reference.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them. Upon a security incident, organizations backtrack to identify the CEP (compromise entry point), remediate the damage, and prevent its recurrence. The main artifacts available for backtracking are trajectory logs, which record agent functionalities, and source code; app(lication)-specific function call logs are often fairly limited. However, trajectory logs are at the agent functionality abstraction layer, while the CEP candidates are function calls at the app code execution layer. Due to this semantic gap, the analyst needs to manually inspect the relevant code for each CEP candidate to infer its corresponding agent functionality. In this work, we present Origin, a backtracking tool for the analyst to submit a small number of queries to identify CEPs that existing tools cannot provide. Our approach poses two challenges: (1) define the intermediate abstraction that captures the mapping relationships between the two semantic layers; (2) determine the region-to-variable mapping for constructing the cross-layer graph defined in the intermediate abstraction. Each region is a specific group of agent functionalities. Origin addresses the challenges by (1) the cross-layer dependency graph (CLDG) that connects region-inferred functions at the semantic level to the variables in the low-level taint propagation subgraph, plus the associated query language, and (2) the region inference algorithm. Case studies on five popular agent applications across eight attack incidents show that an analyst using Origin correctly identifies all the CEPs.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
None explicit
No explicit feedback protocol extracted.
"Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them."
None explicit
Validate eval design from full paper text.
"Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them."
Not reported
No explicit QC controls found.
"Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them."
Not extracted
No benchmark anchors detected.
"Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them."
Not extracted
No metric anchors detected.
"Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
Agent applications are increasingly deployed, yet agent-specific attacks pose real threats to them.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
No explicit human feedback protocol detected.
Evaluation mode is explicit
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.