Could a trick along the lines of the Apple SMC copyrighted phrase be used to poison a protocol against a cloud provider? Release your client and server under a

Could a trick along the lines of the Apple SMC copyrighted phrase be used to poison a protocol against a cloud provider? Release your client and server under a license like AGPL, with an attached file not under AGPL that both components require. It's not possible to say the code is non-free because it's explicitly free, but packaging and placement (such as e.g. default pip installs using a trademarked name) could ensure at least some pain is felt to make a typical client talk to a server that does not have that file. Perhaps the file's license allows to be embedded anywhere so long as it is only used to play the role of a client