How to Configure Make MySQL Read Only Access

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up make mysql read only access by creating a restricted database user. Then you paste those specific login keys into your automation module. Many teams skip this step and use an admin account for speed. Broad permissions let a broken scenario change or delete live data. A read only role keeps your tables safe from bad writes. How make mysql read only access works in practice Make runs cloud scenarios that pull rows from your database on a schedule. The platform needs a host address, a

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up make mysql read only access by creating a restricted database user. Then you paste those specific login keys into your automation module. Many teams skip this step and use an admin account for speed. Broad permissions let a broken scenario change or delete live data. A read only role keeps your tables safe from bad writes.

How make mysql read only access works in practice

Make runs cloud scenarios that pull rows from your database on a schedule. The platform needs a host address, a port, a user, and a password. First, your database admin creates a dedicated user inside the MySQL server. The admin grants only select permissions on the specific schemas the scenario needs. The admin leaves out insert, update, delete, and drop permissions for that user. Next, you open your scenario editor and add the database module. You enter the new read only user keys into the module settings. When the scenario runs, the database checks the user role at login. The server rejects any command that tries to write or delete data. You also need to allow network traffic from the automation platform IP addresses. Teams often pair this role with a read replica to protect primary storage.

What native database roles solve and what they miss

A native read only role stops accidental writes from a broken workflow. It makes sure a bad step in a scenario cannot drop a table. Still, native database roles only check who logs in at the start. They do not inspect what individual queries do while the session runs. A select query can still pull sensitive customer fields from a allowed table. Those fields include emails, phone numbers, card numbers, and national IDs. Once the scenario pulls those rows, the data sits in workflow execution logs. Anyone on the team who opens the scenario history can read those logs. Static database passwords stored in the cloud app also create a risk. If an admin leaves the team, rotating those shared passwords breaks active workflows. Native roles also cannot stop a bad select query from locking up memory. A heavy query without a row limit can slow down your whole database. Also, database logs only show the shared automation user name for every run. You cannot tell which team member built or triggered a specific scenario.

Why read replicas and views fall short at scale

Some teams build custom database views to hide sensitive columns from workflows. An admin creates a view that leaves out emails and card numbers. Then the admin grants the automation user select rights only on that view. This setup works for one or two simple workflows at the start. As the team adds dozens of scenarios, managing views takes too much time. Every new workflow needs a schema change and a review from an admin. Other teams point their automation modules to a dedicated read replica database. A replica keeps heavy queries away from the primary database engine. Yet a replica still holds a full copy of your sensitive customer data. Pulling unmasked phone numbers or national IDs from a replica still exposes data. Teams need a way to rewrite sensitive fields in results without building views.

Auditor Read-Only Access + MySQL Access Governance: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Check MySQL queries and results on the wire

MySQL grants control who logs in. They do not check single queries or mask sensitive columns once a session starts. With hoop.dev, you run an open-source proxy, a sidecar for your MySQL. It runs next to MySQL, RDS, or Aurora and reads the MySQL wire protocol.

Multi-statement batches and prepared queries are split and checked one by one by hoop.dev guardrails. When a rule refuses a query, MySQL returns a native error packet with your message. On the response path, hoop.dev data masking rewrites string values in returned rows that match your rules. Every query and decision is logged per resource. See the MIT-licensed project on GitHub.

Frequently asked questions

Can a MySQL read only user still slow down production?

Yes, a read only user can run large joins or full table scans. These heavy select queries use up CPU and memory on the database server. Using a read replica helps keep that load away from primary traffic.

How do we hide sensitive columns from Make scenarios?

With native MySQL tools, you must grant column privileges or build custom views. Both options require manual database changes every time a scenario needs new fields. Masking rules that rewrite emails and card numbers in results avoid schema work.

What happens when we rotate the MySQL password used in Make?

Every scenario using that database login will fail until you update the password. You must open the connection settings in the platform and save the new key. Using short-lived credentials or central access controls reduces manual password updates across workflows.

The query runs. The emails stay hidden.