Hi @adrianhernandez ,
You're confusing UC catalog permissions with workspace ACL permissions. In UC you have following securable objects on which privileges can be granted:

In Azure Databricks, you can use access control lists (ACLs) to configure permission to access workspace level objects like folders, files, notebooks, computes etc.
You can manage workspace object permissions by adding objects to folders.Objects in a folder inherit all permissions settings of that folder.
For example, a user that has the CAN RUN permission on a folder has CAN RUN permission on the alerts in that folder. If you grant a user access to an object inside the folder, they can view the parent folder's name, even if they do not have permissions on the parent folder.
For instance, a notebook named test1.py is in a folder named Workflows. If you grant a user CAN VIEW on test1.py and no permissions on Workflows, the user can see that the parent folder is named Workflows. The user cannot view or access any other objects in the Workflows folder unless they have been granted permissions on them.
Below you can find all permission that you can set on Folders:
https://learn.microsoft.com/en-us/azure/databricks/security/auth/access-control/#folder-acls

And here'e a list of ACL you can set on notebooks:
https://learn.microsoft.com/en-us/azure/databricks/security/auth/access-control/#notebook

So to sum it up. In my opinion you can't accomplish what you want. Because ACL required to run notebook - CAN RUN permission - already contains also CAN VIEW permission.