In reply to Bridget.

So, you can disable blocks without concern for breaking the site where they may be used, the only catch is that they will end up showing a warning in the editor and ask a user to convert it to HTML. However, I will also say that trying to find the actual names of the individual blocks in a block library plugin, to allow only the ones I want, can be a real pain.

Also, recently Core broken the filtering of embed blocks because they decided to convert them all to block variations of the generic core/embed block. 🤦🏻‍♂️ I opened up an issue on this to point out that they broken documented existing functionality. They didn't bother to note this in their release notes, or apparently even realize they were breaking their own functionality.

Sometimes it appears that Gutenberg has gotten too big and no one actually understands they impacts to other areas when they make changes. They obviously don't have enough automated tests to flag these broken regressions.