- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper studies if command denylists used by terminal AI agents miss alternative commands that would perform the same file system operations. It introduces a system that uses an LLM that is given command documentation to suggest operation-command pairs, checks the effects through sandbox execution, and repairs unsuccessful candidates with execution feedback. The authors collect denylists with rules from GitHub configurations for three agents. For several file system operation types, they report operation-specific incompletely blocked rates. The paper studies differences in agents and repository popularity and studies explanations that include command popularity and versatility. It contributes an empirical characterisation of the limitations of command-based restrictions.
Critical strengths
The inconsistency between command names and the effects from commands is important for agents that execute shell commands. Studying thousands of configurations could help in finding how that problem behaves. I would regard a well-supported characterisation as a useful contribution, even without a new defensive mechanism.
Also, ShellSieve uses the LLM to explore possibilities and execution-based oracles to check the suggested effects. The canary-based checks in their appendix and the feedback-given repair loop should give a great basis for validating individual examples. This seems like a promising design for a systematic way of looking into heterogeneous command capabilities.
Critical weaknesses
There seem to be some central quantitative results that have inconsistencies, which make it less possible to assess their magnitude reliably. Section 5.2 states that 2,718 denialists cover at least one studied operation, while Section 5.3.3 states that 3,091 denial lists incompletely block at least one operation. With their definitions: the latter should be a subset of the former. Section 5.3.3 also reports 214 distinct bypass commands overall, while Table 3 reports an average of 334 and a maximum of 346 distinct read bypass commands per analyst. These cannot use the same counting unit and population as currently described. Are these reporting errors?
It also seems that a command that escapes a denylist may still require approval or be stopped by another control (figure 2 includes that distinction). Appendix A describes another difference in that its auto mode example concerns commands that should be routed to a classifier and not commands that must always be denied. Meaningful findings, but they should be distinguished from successful unauthorised execution through a deployed agent's complete policy.
Questions for authors
-
Can you explain the issue with 2,718 versus 3,091 denial lists and 213 distinct bypass commands versus Table 3's read counts? It would be great if you could please specify the counting units and populations and give per-operation numerators and denominators.
-
For a smaller representative sample, could you show the original rule and protected operation with its specific arguments, the validated alternative command, and the actual agent decision: deny, request approval/classify evaluation, or allow? For Appendix A, what agent version and permission configuration were used? This would help make clear what a gap is in the policy component from a complete approval bypass.
-
How do you check that an alternative command performs the same restricted action on the same protected files while getting past the agent's denylist? Execution on one substituted path establishes that instance, but does not by itself establish all generalised instances.