Part 7 of 14 · 2 min read
Declared capabilities, URL requirements and who is really in control
A client declares what it can do when it connects: elicitation (an empty object means form only; url must be named), sampling (with tools and context sub-capabilities), roots. A server must not send what the client did not declare, and the example gates every request in one function, returning a message for the model rather than a crash.
Warning: a fallback flag is a weaker control
A confirmed=true argument lets the model say "the user agreed". It is only as honest as the model's belief, which is a reason to keep the high-risk actions behind a host-side approval (below) and to use this fallback only where a mistake is cheap.
Beyond screening the address itself, URL mode has requirements the address table above does not capture. The client must show the full address and get consent before opening it. It must never prefetch it. It must open it in a way the client and the model cannot read, and highlight the domain. Accepting means the person agreed to open the page, not that the work finished. The tool must check for completion itself. That is why calling connect_calendar again before sign-in finishes returns "The sign-in is not finished yet" rather than an error. A third party's tokens never pass through the client, and token passthrough is forbidden outright. URL mode is for third-party sign-in and secrets. It is not for how a client authenticates to the MCP server itself (module 5 covers that).
A server that asks "are you sure?" is polite. It is not a control, because the server's author decides whether to ask, and a careless or hostile author simply does not. The same 5000 "gift" expense submitted by submit_expense (which asks) and submit_expense_quick (which does not) both succeeded with no host gateway present. Behind a host gateway that asks the person before running any tool not marked read-only, both submitted 0 -- the person declined, and nothing the server wrote could change that.
Tip: ask with the details, approve with the policy
Make the server's question specific ("Submit 250 for dinner?") so a person can answer well. Make the host's rule general ("any write needs approval") so it cannot be avoided by a server that forgets to ask.