Blueprint Function Library variables can be promoted out of scope

Input parameters can be promoted to variables from the context menu when dropped on an empty graph. Per [Link Removed] this is not expected and dangerous for users to use.

This is reproducible as far back as //UE4/Release-4.22 cl 8065115 so this is not a regression.

1. Open any project
2. Create a new Blueprint Function Libary (BFL)
   • Right click content browser > Blueprints > Blueprint Function Libarary
3. Open the new BFL
4. Create a new function
5. Create a new input variable for that function
6. Drag off the input pin and release the mouse on a the empty graph
7. Select 'Promote to Variable' from the context menu

Result
The input parameter is promoted to a global variable and the BFL can no longer succesfully compile

Expected
Only local variables should be declared within BFLs

How does TextureRenderTarget2D get TArray<uint8> type data?

How do I set a material as a post-processing material?

How to delete some elements correctly when deleting an array loop?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

Why does the REMOVE method of map container remove elements have memory leaks?

What is the difference between Camera and CineCamera?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

How would I go about lerping the rotation instead of it snapping when turning (pls dont sue me epic)

How to assign a value to a member of UMG's UMaterialInterface pointer type in C++?