Emolysis acts with the permissions of the account you sign in with, no more. To work end to end, that account needs to read the catalog, read the tables you want to sample, and create what a deploy makes on your platform, such as a job and its SQL files in your workspace folder on Databricks.
We recommend starting with a development workspace and a role that has only those rights, then promoting through your usual process. The Databricks page lists the known traps the profile catches, including Unity Catalog permissions.
Deploys run under the same account, so production access stays governed by your platform. See connecting Databricks and deploying pipelines.