Verify MCP queries handle new time-window parameter in worker DB queries

Description

Real-time queries to the worker DBs have been updated to include a time window parameter. The front-end uses gRPC for these queries and already works with the new parameter.

MCP queries use a different code path (not gRPC), so it's unclear whether they are affected. It's possible that:

• MCP queries bypass the time-window parameter entirely and still work fine
• MCP queries silently miss the new parameter and return incorrect/incomplete results
• MCP queries need an explicit update to pass the time window

Why Is This Needed

This is a preventive review to ensure MCP queries remain correct after the worker DB query interface changed. If MCP queries don't pass the time window, users querying via MCP could get different results than the front-end UI for the same filter — a subtle and confusing inconsistency.

Action Items

1. Review the recent changes to the real-time worker DB query path that added the time-window parameter
2. Trace the MCP query code path and determine whether it hits the same endpoint/function
3. If MCP queries need the time-window parameter, update them accordingly
4. If MCP queries use a separate path that doesn't need it, document why

Impacted Repositories

• kubeshark