Yes, but maybe not in the way you are thinking. Using the legacy XLATE Route Next Hop by Calling Party Number for this purpose is not going to scale well. Instead, look to Cisco Unified Routing Rules Interface (CURRI) (pronounced Curry).
https://developer.cisco.com/site/curri/The basics of how this works is as follows:
CUCM receives a call to a pattern for which you wish to filter calls for (E.g., an inbound match all ! pattern)
CUCM has this pattern configured with an External Call Control Profile (ECCP)
CUCM sends a request to your web server (as defined in the ECCP), which contains XML about the call such as calling and called number
Your web server then processes business rules, such as which calls are blocked or allowed, and then responds to CUCM with a permit or deny
CUCM then takes the action from the web server and either processes the call further (based on the next pattern in Digit Analysis (DA)), or drops it
