How to Configure Make MariaDB Prevent Delete
To make mariadb prevent delete actions in Make, you restrict the database user role. You give the Make account select, insert, and update rights, and revoke delete rights. Teams often set up Make scenarios with a default admin database account to move fast. When that account has broad rights, a flawed workflow step can wipe out production rows. One bad filter or empty variable in a scenario can clear a whole table. How to make mariadb prevent delete at the database level Database admins star
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.
To make mariadb prevent delete actions in Make, you restrict the database user role. You give the Make account select, insert, and update rights, and revoke delete rights.
Teams often set up Make scenarios with a default admin database account to move fast. When that account has broad rights, a flawed workflow step can wipe out production rows. One bad filter or empty variable in a scenario can clear a whole table.
How to make mariadb prevent delete at the database level
Database admins start by creating a dedicated MariaDB user account just for Make scenarios. You assign this user permissions to read and add rows on specific tables only. You leave out the delete permission and the drop table permission on that role.
When a Make module sends a delete statement, MariaDB checks the user grant table first. The database engine blocks the statement right away and returns a permission error to Make. The scenario stops on that step, and your stored table rows stay safe.
Some teams also use MariaDB before-delete triggers as a second safety net on key tables. A trigger runs before any row removal and checks the active user or row status. If the rule fails, the trigger raises an error signal and stops the removal.
What native grants solve and where gaps remain
Native MariaDB grants work well when an app never needs to remove any data. They stop whole classes of mistakes by locking down what the account can do. They also help teams pass audits by showing clear separation between human and automation accounts.
Yet many real Make workflows need to clean up temporary rows or old sync records. If you grant delete rights for one task, that account can delete anything in scope. Native database roles decide who logs in, not whether a specific query is safe.
End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
A role cannot tell the difference between a single row removal and a missing filter. It also cannot mask sensitive fields like emails or phone numbers in query results. When a scenario reads customer tables, raw card numbers and national IDs flow into scenario logs.
Using soft deletes and stored procedures for Make
To avoid giving raw delete rights, teams often switch to a soft delete pattern. You add a status column or a deleted timestamp column to your MariaDB tables. Make scenarios then run an update statement to mark rows inactive instead of removing them.
Another pattern uses MariaDB stored procedures to wrap any necessary row removals in logic. You grant the Make database user permission to run the procedure, not direct table delete rights. The procedure requires a specific row key and refuses to run if the key is blank.
These patterns lower risk, but they take extra time to build and keep up. Every new table needs its own procedures, triggers, or status columns before you build scenarios. As your team adds more databases and automation tools, managing static grants gets hard.
Inspect every MySQL query and response in flight
Static grants and network rules block bad logins. They cannot pause a risky query for review or mask emails in a result set. By design, hoop.dev is an open-source proxy that runs as a sidecar for your MySQL. It reads plain queries, prepared statements, and cursors on the wire.
First, hoop.dev guardrails block banned actions before MySQL runs them. An AI Analyzer you configure can score intent, and hoop.dev data masking rewrites sensitive string columns in results. Every query and verdict goes to the resource audit trail. Find the open-source binary on GitHub.
Frequently asked questions
Can I block delete statements for just one Make scenario?
MariaDB permissions apply to the database user account, not to individual Make scenarios. To isolate one scenario, you must create a separate database user with its own grants.
What happens in Make when MariaDB blocks a delete query?
MariaDB returns an access denied error to the Make database module during the run. You can attach an error handler route in Make to catch this and alert your team.
Does revoking delete rights stop table truncation too?
In MariaDB, the truncate command uses the drop privilege rather than the delete privilege. You must revoke both delete and drop permissions so the user cannot clear a table.
Related guides
In this post