Skip to content
AdminKit

Elicitation (MCP)

What is Elicitation (MCP)?

Elicitation is a Model Context Protocol capability letting a server pause mid-task and ask the client to collect more information from the user, rather than requesting everything a tool needs up front. AdminKit's guide to securing an MCP server covers why elicitation requests need the same explicit user review as a tool call.

By AdminKit team, Netbase JSC · Updated

Elicitation is a Model Context Protocol capability — part of the protocol Anthropic introduced to standardize how applications connect context and tools to an LLM — that lets a server pause mid-task and ask the client to collect additional information from the user, instead of having to request everything a tool might need up front, or guessing at missing input. The request carries a requestedSchema, a restricted subset of JSON Schema limited to flat objects with primitive properties, so a client can generate a simple form and validate the user’s input before sending it back. The specification requires clients to present an elicitation request to the user for explicit review rather than auto-filling or auto-approving it, and servers are barred from using elicitation to request sensitive information such as passwords or other credentials through this channel. Because an elicitation prompt is server-authored text shown to the user mid-session, it’s also a path a malicious or compromised server could misuse to phish for information under a trusted-looking prompt, which is why the same explicit-confirmation discipline recommended for tool calls applies here too. MCP’s sampling primitive is gated the same way, requiring the client to let the user review and approve a server’s request before it reaches the client’s own model.

AdminKit groups elicitation (MCP) under its AI agents & MCP cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What must a client do before fulfilling an elicitation request?

Present it to the user for explicit review, since the specification requires that rather than auto-filling or auto-approving it on the user's behalf.

What information is a server barred from requesting through elicitation?

Sensitive information such as passwords or other credentials -- the specification bars using elicitation as that channel.

How is elicitation gated the same way as MCP sampling?

Both require the client to let the user explicitly review and approve the server's request before it proceeds, rather than acting on it silently.