Part 7 of 14 · 1 min read
What the host must do
The protocol gives the host a pipe and a vocabulary; it does not give the host good judgement.
The protocol standardises how messages move; four jobs stay with the host, and the example has a small test for each.
- Prefix tool names. Tool names are unique only within a server, not across servers: the example's two servers both offer
search, giving seven tools but only six unique names without a prefix. The host gives the modellibrary__searchandcalendar__searchand routes by the prefix. - Show the model ordinary function schemas. The model never sees "MCP" at all; the host converts each tool definition into the same function-calling shape from Level 2, and the model picks from that list exactly as it always did. MCP is how the host found and executes the tools, not a new interface the model has to understand.
- Ask for consent, and distrust claims. A tool's annotations (such as a hint that it is read-only) are text written by the server's author, and the specification says clients must treat them as untrusted unless they come from a trusted server. The
tidyserver's hint-trust result above is this rule made concrete: believing an untrusted server's own claim about its tool let a destructive call through with zero prompts. - Keep the conversation. Servers get only the arguments of the calls addressed to them. The host is the one place that sees everything, which is also why the host is the place to enforce the gateway from module 1. Scopes, rows, caps, quotas, approvals and the audit log apply to MCP tools exactly as to any tool you wrote yourself.