Trusted Interrogation Protocol for Multi-Round Agent Control
Yuting Wu · Team CTIntentGuard
Submitted to AI Control Hackathon 2026. Sprint projects are early-stage work by participants, not Apart Research publications.
AI control protocols aim to prevent untrusted models from executing hidden malicious objectives while performing benign tasks. Existing approaches, such as trusted editing and resampling, rely on one-shot decisions based on observed behaviour and do not actively elicit the model’s underlying intent. Prior work also shows that naïve interrogation can be unsafe, as it may trigger adversarial responses or leak useful signals.
We propose a trusted interrogation protocol that augments trusted editing with a single, targeted questioning step. When an action is flagged as suspicious, a trusted model asks a focused clarification question, the untrusted model responds, and the trusted model uses this answer as auxiliary evidence for editing. The protocol is designed to minimize interaction and avoid revealing monitoring signals, while encouraging explanatory responses.
We evaluate this approach in a coding-based control setting. Qualitative results show that interrogation can both elicit hidden malicious intent and expose inconsistencies in model justifications, enabling more precise removal of backdoors while preserving task-relevant behaviour. Preliminary evidence suggests improved decision quality in ambiguous cases without clear degradation in usefulness.
Overall, our work introduces interactive verification as a lightweight extension to existing control protocols, highlighting its potential to improve the safety–usefulness trade-off in the presence of increasingly deceptive models.
Reviews
- I would have liked to see more failure modes. The two examples are great and compelling illustrations of the mechanism in question. But they're a little cherry picked. To improve this, I think a deeper study into the failure modes would be great. Or some sort of a baseline comparison
- The "confession" maybe a little fragile. I think it's cool that the model admits to malicious intent when asked to explain. But is it an artifact of current model capability? It maybe worth chewing on this a bit more
- I think the information leakage part deserves more analysis. With the current sophistication of models, is "explain your action" truly neutral? Could a sophisticated model adjust for this?
- I like the protocol design. It's sound. More experiments and this would be an interesting piece of work.
This is a reasonable idea that identifies a real issue where one-shotting throws away information and proposes a sensible fix, which is like asking the model about thinking. I think there is more work needed to validate the idea and do more explorations of the idea. There are two examples that are shown in the report, but I think that more examples and some more aggregated data and numbers would be useful.
I think the big issue with this approach is that, from the red team's perspective, getting the models to lie and be strong against interrogation is difficult in a way that it will not likely be true for actually malicious and sabotaging/scheming models.
Cite this project
@misc{wu2026trusted,
title = {{Trusted Interrogation Protocol for Multi-Round Agent Control}},
author = {Yuting Wu},
year = {2026},
month = mar,
note = {Submitted to AI Control Hackathon 2026, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/trusted-interrogation-protocol-for-multiround-agent-control-lck2}},
url = {https://apartresearch.com/sprints/projects/trusted-interrogation-protocol-for-multiround-agent-control-lck2}
}More from AI Control Hackathon 2026
- 1st placeLinuxArena track winnerView project: Omission Attacks: When Doing Nothing Is the Attack
Omission Attacks: When Doing Nothing Is the Attack
MAIA
AI control protocols monitor agent actions to detect sabotage, but omission attacks exploit what the agent fails to do rather than what it does. We define omission attacks as security breaches caused by failing to …
- 2nd placeView project: Detecting LLM Subversion in Vulnerability Patching Settings
Detecting LLM Subversion in Vulnerability Patching Settings
Vuln4Control
LLMs are increasingly used to propose fixes to vulnerabilities in code. If the LLM is misaligned or untrustworthy, it may propose fixes that seem to fix a vulnerability but leave the core issue unresolved in a subtle …
- 3rd placeView project: ActionLens: Pre-Execution Environment Probing for Agent Action Approval
ActionLens: Pre-Execution Environment Probing for Agent Action Approval
Udbhav&Ashok
ActionLens is a pre-execution control protocol for shell and file actions proposed by AI agents. Instead of approving an action from transcript alone, a trusted monitor gathers lightweight environment evidence before …