{"version":"2.1.307","anchor":"elicitation-responses-masked-in-logs","canonical_anchor":"elicitation-responses-masked-in-logs","heading":"Sensitive answers to MCP server questions are hidden in debug logs","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/elicitation-responses-masked-in-logs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Sensitive answers to MCP server questions are hidden in debug logs\n\nWhen 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\n\n**Unclear.** It is unclear which fields count as sensitive.\n\n**What**\n\nAn 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.\n\n**Why**\n\nSecrets 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.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}