Evidence · DiggingBeagle record
LiteLLM issue 48169: virtual MCP call double-counts limits
Reporter-provided reproduction of double limit reservations, omitted tool pricing and absent spend logging.
- Published
- Oct 24, 2026
- Source role
- primary disclosure
Evidence record
Reporter-provided reproduction of double limit reservations, omitted tool pricing and absent spend logging.
Claim-level citations (3)
- supportsLiteLLM virtual MCP tool calls double-reserved limits but missed actual tool cost logs: The reporter observed two counted requests for a single virtual mcp_tool_call: rpm_limit 4 accepted only two such calls, max_parallel_requests 1 refused a single virtual call, and the configured direct-tool charge was absent.
Issue 48169, Actual behavior and comparison to direct tools/call
- supportsLiteLLM virtual MCP tool calls double-reserved limits but missed actual tool cost logs: The reporter observed two request/concurrency accounting checks around one mcp_tool_call wrapper invocation, including failure at max_parallel_requests=1.
Steps to reproduce; quota observations
- supportsLiteLLM virtual MCP tool calls double-reserved limits but missed actual tool cost logs: The reporter reports a configured underlying MCP tool price of 0.25 that was billed through direct calls but not through virtual wrapper calls, alongside missing spend records.
Pricing and spend logging reproduction