---
title: "Comment by Kartik N V J K on \"What would it take to make agent context useful without making access broad?\" | Hashnode"
description: "This is the right framing: the failure is that the output looks fine while the permission model is quietly wrong, which is the hardest kind of bug to catch beca"
url: "https://hashnode.com/posts/what-would-it-take-to-make-agent-context-useful-without-making-access-broad/6aba70e458dc0108a22c53e0/comment/6ababbad0f249c24b076d906"
---

[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)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

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

This is the right framing: the failure is that the output looks fine while the permission model is quietly wrong, which is the hardest kind of bug to catch because nothing actually errors. Modeling a request as an action with a purpose, allowed sources, and recipient constraints is what I have found actually scopes an agent, far more than handing it the whole workspace and hoping. In the four-layer model, which layer ends up owning the deny decision when purpose and identity disagree?

[Yethikrishna R](https://hashnode.com/@yethikrishnar)

[Sep 28](https://hashnode.com/posts/what-would-it-take-to-make-agent-context-useful-without-making-access-broad/6aba70e458dc0108a22c53e0/comment/6ababbad0f249c24b076d906#reply-6ababea637352f8b07a4c23b)

Thanks, Kartik. I'd put the deny at the identity layer: if the action's purpose and the identity grant don't line up, the graph's candidate context shouldn't make the read or send permissible. The runtime should record that decision so the user can see why it stopped. Would you test that as an explicit cross-layer case in the harness?
