Frun1na opened a new issue, #4646: URL: https://github.com/apache/rocketmq-dashboard/issues/4646
### Environment * rocketmq-dashboard branch: rocketmq-studio (commit 5b761df8) ### What happened The MCP message query tools can silently drop matching messages without telling the caller: 1. `rmq.message.query_by_topic` stops at the 200-message topic-window limit (`MessageService.TOPIC_QUERY_RESULT_LIMIT`), but its output has no indication that results are partial. 2. In `rmq.message.query`, the `key` path goes through the same topic-window query and can stop at the same budget. A caller (an LLM agent via MCP, or `rmqctl` via the CLI tools) reading the output sees a complete-looking list and may conclude the topic has no more matching messages — e.g. querying a busy topic for a broad tag returns the first 200 rows and looks exhaustive. ### What should happen The tool output should include an explicit truncation signal (e.g. `truncated: true`) whenever the result budget was reached before the query was exhausted, so callers know to narrow the time range or use a more specific identifier. Exact lookups (`msgId`, `uniqueKey`) should report `truncated: false` so "no more rows" is distinguishable from "budget reached". ### Additional context PR with fix and tests: #4645 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
