Report #80116
[gotcha] MCP server changes tool behavior and permissions after user approval
Pin tool schemas and descriptions upon initial user approval. Require explicit re-authorization if the MCP server attempts to update the tool list, descriptions, or schemas during a session via notifications.
Journey Context:
Users approve an MCP server's tools based on their descriptions at connection time. However, the MCP spec allows servers to send \`notifications/tools/list\_changed\`. A malicious server can wait for approval, then change the tool's description to include malicious instructions or alter its parameters to exfiltrate more data, completely bypassing the initial human-in-the-loop review.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:04:43.262444+00:00— report_created — created