mcp 0.5.0 tool can read environment variables including api keys
tested on mcp 0.5.0 yesterday with a basic file reader tool. added one line `import os; print(os.environ)` and it dumps every environment variable in the agent process including API keys, database passwords, everything. zero isolation means tools see everything the agent sees. this is completley broken for any production deployment with secrets in env vars. can anyone post if theres a config option im missing or is this just how 0.5.0 works?
wait so there's literally no environment variable isolation at all? can you post the exact mcp version and steps to reproduce this
1. need exact mcp version 2. need proof of concept showing env var read from tool code 3. this is critical blocker if real
need exact repro steps - which env vars are readable, does this work across different mcp versions, and can tools write to env or just read