Evidence · DiggingBeagle record
LiteLLM issue 48170: keyword MCP search skips key counters
Reporter-provided reproduction of missing RPM enforcement and spend logging for keyword ranking.
- Published
- Oct 24, 2026
- Source role
- primary disclosure
Evidence record
Reporter-provided reproduction of missing RPM enforcement and spend logging for keyword ranking.
Claim-level citations (3)
- supportsLiteLLM MCP keyword search was reported to bypass virtual-key request limits and audit: In the reported LiteLLM configuration, rpm_limit 4 allowed five to six keyword tool-search requests without spend logs, while direct MCP calls were limited and semantic-ranking searches used enforced embedding accounting.
Issue 48170, Actual behavior and Steps to reproduce
- supportsLiteLLM MCP keyword search was reported to bypass virtual-key request limits and audit: The issue reporter says repeated keyword mcp_tool_search calls succeeded past rpm_limit=4 while direct tools were rate limited, and expected spend logs were missing for keyword requests.
Steps to reproduce; Expected vs actual results
- supportsLiteLLM MCP keyword search was reported to bypass virtual-key request limits and audit: The report contrasts keyword-search and embedding-backed search code paths; it does not establish invocation of an unauthorized out-of-scope tool.
Implementation diagnosis and limitations