While this looks like a nice idea on paper, I would not recommend to use the current implementation of &#x27;maybe&#x27; on a system that hosts valuable data.<p>The tool seems to work by intercepting individual &quot;blacklisted&quot; system calls and then - instead of executing them - returning a nonsense value.<p>The issue is that this breaks every single POSIX spec and will therefore break any program that does more than a few trivial IO operations and relies on those operations to behave as specified.<p>So it might work for a simple demo case where a small script only does a single file modification and never checks the results, but for any serious program (think a database, a complex on-disk format or really anything that does network IO) this will lead to corruption and undefined behaviour as system calls will return erroneous success values or invalid file descriptors.<p>I think to actually make this work one would have to emulate the system calls and make sure everything stays POSIX compliant. Doing this correctly for calls like mmap might get tricky though (and won&#x27;t be possible from within a python runtime). And even then it isn&#x27;t obvious how something like network IO would be handled.