This lack of throttling could allow a malicious actor to potentially brute-force the GUID and download confidential files from the database.
If your security and logic is set correctly I do not see this scenario happening. What in my opinion is more likely is that the the app performance can be influenced negatively, at such level that it might shutdown and restart. Not saying that this is okay because this can also be abused for unwanted behaviour...
An option could be to add parameters with an offset and amount so you have more control on the requests. When a requests hits the limit the requester will be required to do an additional request with a changed offset.
This module could be interesting too: Ratelimiter for Mendix I do not have experience with this module but it might add some options in your search for a fitting solution.
[edit]
In addition:
Mendix Restrict Access for Incoming Requests
Implement Mendix Best Practices for App Security
From what I understand after reading more carefully, you are wondering when someone manipulate the guid eg:
https://application.mendixcloud.com/file?guid=55555143618734444
Towards
https://application.mendixcloud.com/file?guid=55555143618734445
In that case I would say with how I started my answer: security. If your domain model and entity access is set correctly than this can not be abused and will return a 401 error.
Which might be an interesting read:
https://community.mendix.com/link/space/app-development/questions/105768