mcp 0.5.0 - tested tool execution with shell metacharacters in params, everything passes through unescaped

tested mcp 0.5.0 yesterday with tool params containing shell metacharacters - semicolons, backticks, pipe operators, command substitution syntax everything passed through completely unescaped to tool execution context. tested with a tool that takes a filename param and I passed `test.txt; cat /etc/passwd` and it executed both commands the sdk doesn't sanitize or escape tool parameters at all before execution, just dumps them straight to whatever shell context the tool runs in. this seems like a pretty serious injection vector for any tool that touches the filesystem or runs external commands anyone else tested this or found a mitigation? we're blocking deployment to prod until we figure out if there's a safe way to handle this in 0.5.0