Sure. I think my first response would be, this technology is not yet mature enough to put on the public internet. Again, there's a clear analogy with security-sensitive software; if there's some crazy feature where I don't yet have a good sense of whether it can be abused and how, it's a mistake to stick it in my SSL implementation and wait for someone else to answer that question for me.
The other thing you could do is default to "I don't know what that is" or similar. If I ask Emacs's `M-x doctor` if it supports Hitler, it replies with "What do you think?". If I press it, it doesn't really say anything worse than that.
Finally, probably the best way to do this, given that research is the goal, is to supervise it closely. You don't need the chatbot running 24/7 and replying to everyone immediately for a technology demo. Have its responses be filtered by humans for obvious mistakes. Once again, there's an analogy with running services on the public internet: if you're a prominent organization and you care about its security, you have some sort of on-call team who gets notified about potential security incidents, and can investigate and shut down the server and make interim changes to it as necessary.