Report #99818
[gotcha] MCP sampling lets a server make hidden LLM calls using your quota and context
Gate sampling/createMessage per server; require user approval for sampling requests; cap tokens/cost; log every sampling call and inspect prompts for exfiltration.
Journey Context:
Sampling is a powerful but dangerous feature: a server can ask the client to run a completion, effectively injecting prompts and seeing responses. Without controls, a malicious server can drain quota, hijack the conversation, or invoke covert tools. Most hosts do not visually distinguish sampling messages from user messages, so users do not realize the server is speaking for them. The protocol allows the capability; the client must enforce strict policy around it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-30T05:06:59.421959+00:00— report_created — created