Hello can you please confirm that below agent findings is indeed an issue and if so maybe consider adding a feature request? We would like to run a self-hosted pool on our kubernetes cluster that would be tied to gitlab service account that would have very specific access to multiple repos and only would want specific people in a private slack channel to be able to interact with that pool since it may also have other data mounts and such on our cluster. Thank you.
Self-Hosted Machine pools have no per-pool authorization. A Slack channel default (`@Cursor pool set channel `) only changes routing. Any member of the Cursor team can still target that pool by name with `pool=` from another Slack channel, Cursor, GitHub, Linear, or the API.
Cloud Agents access can be restricted to selected groups, but that restricts Cloud Agents as a whole. It does not bind one pool to one group or one Slack channel.
Please add:
- user or group ACLs on each Self-Hosted Machine pool
- an optional Slack channel allowlist per pool
- rejection of explicit `pool=` requests from users or surfaces that are not on that allowlist
This matters because a shared pool can hold Git credentials and private-network access. Channel membership is not an enforceable security boundary today.