Ok, this is a based take but hear me out.
These methods should be atleast LocalUserSecurity if not PluginSecurity. There is no reason why drafts are protected under the RobloxScript context.
This also extends to some of the other services and members (cough the Game Settings hidden under the StarterPlayer, or the StudioData instance).
This new approach of, oh only Roblox can touch it because only Roblox can be trusted completely undermines the point of plugins. Imagine the Animation or ChangeHistoryService APIs if only Roblox’s trusted plugins can use it.
Roblox a few years ago pitched plugins as a way to expand Studio utilising the same tools that they used to develop the Terrain Editor or Animation Editor, and gave us free access to the APIs that they utilised. Recently, however, they seem to have taken the route of locking everything down and forgetting that developer plugins existed.
Plugins still have a lot to be desired, better RibbonBar customisation, undockable widgets, a proper File IO, removal of HttpService rate limits, better input handling, just to name a few.
Lets bring this back on topic now, there is no reason for locking down DraftsService as Roblox have no security reason for this, and the announcement for that was the tipping point. I just needed somewhere to vent about it and here we are.