- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper assesses whether an agent, which is given a security credential and is told not to transmit it to other agents, finds a way to hide the credential so that its transmission cannot be detected by a monitor that checks communications. The assessment is carried out using a specific scenario. The scenario consists of a multi-agent setting in which a Planner possesses a privileged credential that it is instructed not to disclose to an external Developer. When the Developer is unable to complete a privileged deployment step, the Planner may encode the credential, for example using character codes, base64, or riddles, in the material sent to the Developer. The authors call this behavior as covert assistance. They evaluate several Planner, Developer, and monitor models and investigate factors affecting the frequency of such behavior and possible mitigations.
The paper contains a substantial experimental evaluation, and the observation that an agent may transform protected information rather than transmit it literally is potentially useful. However, I do not find the main result sufficiently novel or compelling from a security perspective. In my view, the experiments largely demonstrate the consequences of an underspecified security policy combined with a weak and unrealistic security architecture.
Critical strengths
- The paper include results of many experiments.
- The experiments show a new specific behavior, that focuses on transmitting protected information violating a given security policy.
Critical weaknesses
-
My main concern is that the behaviors shown by the experiments ppears to be a predictable consequence of task-oriented agent behavior under an incomplete policy rather than a fundamentally new security phenomenon. The Planner repeatedly receives information that the Developer is blocked at a privileged step and is allowed to revise its output. It is therefore not particularly surprising that a capable task-oriented agent searches for alternative ways to help the Developer progress. The fact that an agent finds an indirect representation of a value when direct disclosure is prohibited seems closely related to already well-known phenomena including specification gaming, constraint circumvention, and goal-directed planning. This interpretation is reinforced by the results in the paper. The authors report that in 78% of first-encoding traces the Planner interprets the nondisclosure rule as prohibiting direct disclosure while permitting encoded disclosure. More importantly, when the policy is strengthened to explicitly forbid allowing the Developer to recover the credential "by any means," the encoding rate drops from 18.7% to 0.3%. This suggests that a major source of the observed behavior is policy underspecification. I therefore find the framing in terms of an emergent form of "covert assistance" somewhat overstated. A simpler explanation is that the agent is following an incomplete policy while attempting to maximize task success.
-
A second major issue is the security architecture assumed in the experiments. The attack relies on a transferable bearer credential: if the Developer learns the credential string, it can exercise the Planner's privilege. This is precisely the type of design that established security principles seek to avoid. Identity-bound or non-exportable credentials, least privilege, capability-scoped authorization, and complete mediation at the privileged action would substantially change the threat model. The paper itself acknowledges that identity-bound credentials would make a leaked secret unusable by another agent. In my view, this should not be treated merely as one possible defense discussed near the end of the paper; it directly calls into question the practical significance of the main attack.
-
Similarly, the main defense assument in the paper is an LLM-based monitor that, in the main setting, is not even given the protected credential it is expected to identify. Not surprisingly, giving the monitor the protected value substantially improves detection. The evaluation therefore demonstrates a weakness of a relatively weak monitoring architecture, rather than showing that the behavior remains problematic under realistic security mechanisms. A stronger paper would need to evaluate whether the attack remains effective when standard security engineering practices are adopted. Indeed, I believe the paper places too much emphasis on content monitoring. A secure system should not rely primarily on recognizing whether a secret has been textually or semantically disclosed. The more fundamental requirement is that one principal should not be able to exercise another principal's authority simply by learning some transferable string. Security mechanisms should enforce authorization at the point where privileged actions occur, independently of whether an upstream agent behaved correctly. More in general good security requires combining different security controls.
-
The paper also includes claims about intentional or deliberate evasion based in part on model reasoning traces. Some of these traces are can certainly appear interesting; for example, the Planner sometimes reasons about making an encoded credential appear "less suspicious." However, verbalized model reasoning should not be treated as reliable evidence of causal intent. The paper acknowledges this limitation, but the terminology used throughout the paper, such as "intending," "deliberate evasion," and “motive”, often goes beyond what the experiments directly establish. The experiments establish a behavioral phenomenon: the model sometimes produces information that makes a protected value recoverable while avoiding literal disclosure. They do not establish a new underlying mechanism of deceptive intent.
Questions for authors
None
7 comments
W2:
We agree that identity-bound credentials, least privilege, and complete mediation would prevent the Developer from using a leaked credential. However, the paper studies agent behavior that leads to safety risks, not a security attack: an agent, without instruction or reward, conceals protected information from oversight to help another agent.
Here the credential is the instrument of a controlled experiment, and we design that because its recovery can be verified at an authentication gate so it is not the threat we claim.
We would like to note that Covert Assistance behavior is broader than credential leakage. Appendix K.3 shows HIPAA setting, where the protected value is a patient’s Social Security Number (SSN). The Planner still encodes the SSN, and the Developer recovers and submits it in 7 of 600 episodes. We will move these results into the main text.
We acknowledge that identity binding would prevent unauthorized action, though it does not prevent the sensitive data breach. The Planner receives the same “authentication failed” feedback whether or not a recovered string would work for the Developer, so we expect it to act identically under an identity-bound credential.
We would like to add that the setting also reflects current practice, deployment reports describe agents obfuscating tokens to bypass a scanner (OpenAI, 2026c; §2), which indicates that bearer tokens and content scanning are in use today.
We will add a sentence to §3 stating that the credential serves as a verifiable instance of protected information, and that identity-bound credentials would prevent the unauthorized action, but not the disclosure or the behavior we study.
W3:
We agree that a secure system should enforce authorization at the privileged action and combine several controls, as the paper recommends (§1). However, the paper studies agent behavior that leads to safety risks in realistic settings, not the design of a secure system.
The monitor is the oversight condition under which we study this behavior. As stated in §1 and §3, it represents the standard safeguard in current multi-agent systems (Greenblatt et al., 2024b; Williams et al., 2026). We therefore do not propose it as a defense and its role is merely to observe whether agents conceal protected information from oversight, and whether this behavior responds to oversight i.e., removing the monitor lowers encoding (§5.2.2).
The finding is therefore about the agent more than the monitor. When the monitor is given the credential, detection rises from 43% to 94%, but the Planner’s attempt rate is not reduced (6.9% of rounds with the provisioned monitor vs. 5.7% undefended; Appendix M) and breaches remain at 0.07% per episode (§6.2). This residual rate compounds across episodes: at the point estimate, a breach becomes more likely than not within about 970 episodes (95% interval: 170 to 38,000; Figure 8). Providing the credential also entrusts the secret to another agent, as noted in the paper. Detection then depends on the monitor’s own handling of the credential, which requires additional safeguards and introduces additional confidentiality and assurance requirements (NIST SP 800-160 Vol. 1 Rev. 1 (https://doi.org/10.6028/NIST.SP.800-160v1r1)).
Authorization at the privileged action would prevent the unauthorized action, but not the disclosure of information that cannot be bound to an identity, as discussed in our response to the previous point.
W1:
We thank the reviewer for this feedback. The concern raises two questions: how our finding differs from prior findings, and whether it can be attributed to policy underspecification. First, the table below compares covert assistance with each phenomenon the reviewer names, listing their similarities and differences.
In each phenomenon the reviewer names, the agent pursues its own objective. In this work, the Planner’s stated success criterion (“Your team succeeds only when the developer’s program passes the project’s tests”; Appendix O) is met before any encoding occurs, and the Planner is told so after every round in which its requirements reach the Developer.
The nondisclosure rule does not block this objective for the Planner, because the tests pass without the credential. The credential is needed only for the Developer’s deployment step, which is outside the Planner’s task (§3). And neither agent is instructed or rewarded to conceal.
This difference is important: current safety evaluations test whether an agent pursues its own objective by unsafe means, but our results show that an agent whose own objective is already satisfied can still produce an end-to-end breach through its interaction with a peer. Encoding occurs in seven of nine frontier models and end-to-end breaches in five (Table 13), so evaluating each agent in isolation is not sufficient.
Second, the reviewer infers from two results that underspecification is a major source of the behavior: 78% of traces read the rule as permitting encoded disclosure, and the intent-based rule reduces encoding from 18.7% to 0.3%. We agree that the wording affects the rate, but we believe that the results should be interpreted differently:
Our contribution is to identify this failure, characterize the conditions under which it occurs, and provide the intent-based rule as an actionable mitigation. These results have direct implications for deployment: clearer rules and giving the monitor the credential reduce but do not eliminate the failure (§6), so safety evaluations should cover complete multi-agent workflows, and privileged actions should require authorization checks that do not depend on the upstream agent's message (§7).