Current MCP rate-limit status for the caller — the SAME bucket /api/mcp/tool enforces against.

It previously reported on a different identity in a different store, so it read zero for every caller in every configuration: with Redis up the limiter returns before the deque is ever written, and with Redis down the deque is keyed by the identity string (ip:1.2.3.4) while this read looked up a bare 1.2.3.4. An agent developer saw "remaining: full" and then got a 429 — the meter was worse than no meter, because it was believed.