Limit Scope of API Token to Resource(s)

I’m looking to use the DO API to update Firewall entries from a web-application. The hope is to allow clients to access critical application services 24/7 without worrying about anything like DDoS from an external source (there is still an internal source risk, but being that this is a paid service, the risk is much lower and traceable/blockable).

It seems like there is still only read-only and read-write scopes on tokens. This seems like a blatant overlook from a security stance, especially considering there can be multiple projects on one account.

In addition, it would be nice to disallow my CI/CD from having access to my entire server infrastructure when it only needs image repo access. I’m thinking I might need to stop using DO repos altogether and get a Docker subscription or something because it’s just too risky. I like DO because it’s one of the cheaper options, but it’s just not practical. Maybe I can integrate directly with Gitlab? But then I’m limited to one repo and I produce several projects (and tagging wouldn’t make sense for them).

For the Firewall I’m also thinking I might be able to use Cloudflare with their API. Scoping wouldn’t be a problem because it’d be isolated to that platform.

So there are solutions, but all of this seems like it could just be easily resolved by allowing more granular scopes with API tokens.

Would love to hear your thoughts on this, thanks!