I think you are getting confused between Script Registration and Query Definition. You can use parameter placeholder strings (eg ~POVLOC~) in Query Definition. The parameters you create on Script Registration supply the replacement strings for the parameter placeholders. As far as I know you cannot use the parameter placeholders in the queries for Script Registration. I haven't found a way of intercepting the creation of the script parameters to do what you want.
The only thing you could do is a check on the selected WBDLR once the parameters have been selected. If the user picked a WBDLR that is not valid for their location, raise an error and stop the script.
Thanks for your response. You are right.
I have found the other way - to use the 'POV Rule' Parameter in Script Registration - it resolves my issue.
The end-user can able to see only DLRs which related to users' locations.
Unfortunately, we can't search in Query Definition and the user can able to see all Budgets (Target options for WB DLRs) and need to choose the correct option to their rule.