MCP guardrails
Personal-data masking does not stop a tool from deleting rows. Guardrails run on the gateway before the upstream call.
Read-only mode
Allow tools whose names are reads (get, list, search) and refuse mutators (create, update, delete) while you prove a workflow. This toggle exists on every plan.
Allowlists
Team and Agency plans can expose a subset of a large upstream server. That also keeps unused tool schemas out of the model context.
Arguments
Refuse a call when an argument matches a dangerous pattern such as DROP, TRUNCATE, or a blanket delete. Agency plans can differ by client workspace.
The database role should still be least privilege. The gateway is a second gate, not a replacement for it.