Proposal: Sanitize error notifications sent to MCP clients (SafetyCard review)

[boundbench-admin]

We reviewed Superset's MCP service (superset/mcp_service) with SafetyCard, an open-source scorecard of how well AI agents and MCP servers limit the damage when something goes wrong. One suggested safeguard below.

Route ctx.error notifications through the existing error sanitizer (execute_sql.py#L282-L286). Logs and error responses are already scrubbed of connection strings, tokens and emails (middleware.py#L135), but some tool progress notifications still send raw exception text to the client. Routing them through the same sanitizer gives clients the scrubbed text the logs already get.

The full review has other suggested safeguards: https://safetycard.dev/github.com/apache/superset/superset/mcp_service

If something here is wrong or out of date, please let us know here or through the correction form.