---
title: "Comment by Vlad Zoff on \"What would it take to make agent context useful without making access broad?\" | Hashnode"
description: "I'd also carry those constraints through to the output, not stop at retrieval. An agent may be allowed to read two sources separately but not combine them into"
url: "https://hashnode.com/posts/what-would-it-take-to-make-agent-context-useful-without-making-access-broad/6aba70e458dc0108a22c53e0/comment/6ae833d46ead3872ff3a7460"
---

[Discussion](https://hashnode.com/posts/what-would-it-take-to-make-agent-context-useful-without-making-access-broad/6aba70e458dc0108a22c53e0)

Comment [What would it take to make agent context useful without making access broad?](https://hashnode.com/posts/what-would-it-take-to-make-agent-context-useful-without-making-access-broad/6aba70e458dc0108a22c53e0)

[Vlad Zoff](https://hashnode.com/@vladzoff)

[Nov 2](https://hashnode.com/posts/what-would-it-take-to-make-agent-context-useful-without-making-access-broad/6aba70e458dc0108a22c53e0/comment/6ae833d46ead3872ff3a7460)

I'd also carry those constraints through to the output, not stop at retrieval. An agent may be allowed to read two sources separately but not combine them into a summary for a recipient who can only access one of them. So the policy needs to cover both source access and destination constraints, including derived content. Otherwise narrow retrieval can still result in a broader disclosure.
