Last reviewed
Correct answer: A. Nothing yet: it shows the full URL and waits for consent, and the server learns only whether consent was given.
Explanation
The principle — URL mode exists to keep an interaction away from the client and the model, and its rules follow from that one purpose.
Why the key is correct — URL handling: For URL mode, clients show the full URL and gather explicit consent before opening it, and never fetch the URL automatically. So two minutes of silence is simply two minutes of waiting. As for the outcome, the boundary is deliberate: the client only learns whether the user consented. The interaction itself — a login, an authorisation, a payment — happens between the user and the site.
Why the others are wrong — Opening the link unprompted and pre-fetching the page are both ruled out by the same sentence. And a record of what the user did at the far end is more than the client itself knows, so it cannot be passed on.
Remember this — Show the URL, wait for consent, report the consent and nothing else.
Sources — MCP first-party documentation.
Sources
“URL handling: For URL mode, clients show the full URL and gather explicit consent before opening it, and never fetch the URL automatically.”
“The client only learns whether the user consented.”
Practise 10 questions on this topic
Take MCP Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.