You have an agent running on your local system. You want it to have access to a restricted set of things, both locally and remote. What is the technical mechanism you use to ensure that it has a subset of the access that you, as an individual logged into the same system, do?

(I am uninterested in "Don't run an agent" because while yes I see your point that doesn't mean it's not happening and security professionals have to deal with what's happening not what we want to be happening)

@mjg59 Very thought-bubble thinking, but a docker container. Things it needs access to either volume mounts or in the environment, and an allow-list firewall.
@stibbons Ah yes but how does it gain the ability to authenticate to remote services and how do we then ensure that those tokens can only be used for that purpose

@mjg59 @stibbons It kind of feels like the macaroons paper could help with. Although it stopped short of defining a format for tokens or some standard caveats.

I'm sure I'm using some systems where the OAuth tokens are processed as macaroons by the server, but I don't have the information needed to generate restricted sub-tokens.