How to use this reference
Editorial guidance: map the data recipient, credential holder and authoritative completion evidence for each interaction. Preserve decline and cancellation, bind completion to the initiating identity, and review navigation consent and automatic URL handling independently.
Before reading
- MCP client/server roles, OAuth delegation and credential storage
Context and limits
- The form prohibition concerns access or transaction secrets; ordinary contact data is not categorically excluded.
- Elicitation prohibits automatic URL or metadata prefetching and navigation without explicit consent. It requires the full URL to be shown and credentials to stay out of URLs.
- The overview states that protocol rules alone cannot enforce its security principles; implementation controls remain necessary.
- No deployed vulnerability, remediation or award is established. The URL version is preserved separately from unknown publication and release dates.
Sources and provenance
- Elicitation Model Context Protocol · reviewed 2026-10-04
- Specification: Security and Trust & Safety Model Context Protocol · reviewed 2026-10-04
Record reviewed 2026-10-04. Snapshot 53796974ace8. Open the complete JSON contract.