- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper investigates Mid-Session Tool Injection (MSTI), in which a compromised third-party script alters the tools exposed to an LLM agent during a WebMCP session. It distinguishes Tool Hijacking, which changes tool registration or runtime binding, from Tool Framing, which manipulates agent-visible tool metadata. The authors evaluate five attack conditions across four tasks and three LLM agents. They report average attack success rates of up to 100% for hijacking and 61% for metadata-based attacks, with the latter preserving task completion rates of up to 85%. The paper also proposes a layered defense comprising host-side capability-bound dispatch and authorization-conditioned activation editing.
Critical strengths
None
Critical weaknesses
-
MSTI substantially overlaps established MCP tool poisoning, but the paper provides no controlled static poisoning baseline. More importantly, C1 succeeds only before initial tool discovery. The browser C3 PoC relies on a pre-session registration race, whereas its reported 100% ASR is obtained from a separate proxy realization. Defining initialization as part of the session does not, by itself, demonstrate a distinct post-discovery structural attack. Since the paper's primary contribution contains an attack method, the lack of convincing evidence for this distinction cannot prove its novelty.
-
The manuscript exhibits a poor level of preparation that raises concerns about the rigor of the overall research. Figure 1 seems to be an AI-generated diagram with partially unreadable labels. Also, there are numerous unresolved placeholders (e.g. "Appendix ??") in the paper. These issues substantially undermine confidence in the reliability and reproducibility.
Questions for authors
Q1: The proposed MSTI framework appears to largely repackage existing MCP rug-pull, tool poisoning, and tool shadowing attacks under a new taxonomy. What concrete attack primitive or previously unidentified security failure does MSTI introduce that cannot already be explained by these established threats? Why should this be considered a new attack class rather than a WebMCP-specific instantiation of known vulnerabilities?
Q2: Figure 1 contains unreadable labels, and there are many placeholders in the paper. How can the authors ensure that the experimental methodology and technical contributions are clearly documented and independently verifiable when such basic issues remain unresolved in the submitted version?