The record layer makes it significantly harder for other users of the record layer API to trample on each other, and makes representing many small databases easier than running multiple FDB instances. There is no protection against one record layer user opening and using another record layer store in the same database. In the end, this is all just keys and values on FDB, and FDB has no native multi tenancy support.
So if all of your clients are using the record layer, then it’s much harder for them to issue a stray
clear_range(\x00, \xff). However, only mTLS would prevent a persistent person from doing so.
The record layer provides structured schemas for your data, schema changes, a query API, secondary indexes, etc., that are all really nice features to have when using FDB. It does not provide per-user QPS quotas, or storage size quotas, and you’d need to build those in to your application at a layer above FDB.