MCP server moves write approval from the model to the user via elicitation
A developer building an MCP server for a store's REST API found that the confirm flag guarding its write tools was set by the model itself, not by a person. The model could skip the dry-run preview or be steered by prompt injection into applying changes. A related problem was that a preview and its write were separate calls with nothing linking them, so the applied amount could differ from the previewed one. To fix this, the server now uses MCP's elicitation feature to show the user the real dry-run numbers and ask for approval directly. The model is not involved in that answer. The author notes that the server still falls back to applying changes when the client does not support elicitation.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in