In-memory privacy shield to prevent context leaks in MCP tools

The easier and more secure way is to just inject sensitive credentials through a proxy service that ideally lives outside of the box in which the agent runs.

Because even if you're doing this in-memory replacement, the content still lives in they system's memory. So, it makes it less obvious to leak a credential, but it certainly doesn't prevent it.

[flagged]