LiteLLM issue 48171: blocked tool listing still callable by name

Evidence record

Reporter-provided configuration and contrast between MCP discovery guard and direct invocation; fix unverified.

Read the original source ↗

Claim-level citations (3)

• supportsLiteLLM guardrail hid a prohibited MCP tool but did not block direct invocation: The issue reporter reproduced a denied tools/list entry that remained callable via tools/call using the exact tool name; the test did not establish theft or a fixed upstream release.

  Issue 48171, Description and reproduction path comparison

• supportsLiteLLM guardrail hid a prohibited MCP tool but did not block direct invocation: The issue reporter shows a default-on pre_mcp_call rule filtering tools/list based on description while a direct known-name tools/call still reaches the test tool.

  Issue body: Description, reproduction, expected versus actual

• supportsLiteLLM guardrail hid a prohibited MCP tool but did not block direct invocation: The report concerns tested LiteLLM 1.105.1 behavior and does not identify a confirmed corrected upstream version.

  Environment details and maintainer status