Report #2223
[gotcha] MCP list operations silently overflow context because the client assumes the whole list fits
Implement cursor-based pagination for tools/list, resources/list, and prompts/list; bound page sizes server-side; never assume 'listed == injected into model context'; log actual injected token counts.
Journey Context:
MCP supports pagination for list operations, but page size is server-determined and many clients ignore cursors. A server returning thousands of resources/tools can push the context budget over the edge before the user's task even starts. The spec says clients MUST treat cursors as opaque and SHOULD support both paginated and non-paginated flows. If you do not paginate and account for it, the model silently truncates or the client OOMs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:09:39.468268+00:00— report_created — created