How about a wrapper method around DBI::connect to restrict access to the database? You'd have that utility method and possibly others accessible in the Safe compartment but the core DBI methods would remain uncallable.