Sensitive answers to MCP server questions are hidden in debug logs
When you answer a form from an MCP server, fields treated as sensitive are now shown as "[masked]" in the debug log, but the server still gets the real answer
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.307,
ImprovementsSection of the release
Unclear It is unclear which fields count as sensitive.
What
An MCP server, an outside program that gives Claude Code extra tools, can ask you to fill in a short form. This is called an elicitation. Claude Code writes your reply to its debug log, a file of technical details kept for troubleshooting. Fields it treats as sensitive now appear in that log as "[masked]" instead of the value you typed. Previously the whole reply was logged. The server still receives your real answer.
Why
Secrets you type into these forms, such as keys or passwords, stay out of debug logs that you might share or that could be read later.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear which fields count as sensitive.