litellm/tests/mcp_tests
tin 33a92bd48f fix(mcp): keep REST tool listing in step with key/team grant enforcement
The REST listing filter matched key/team grants through _tool_name_matches, which after the prefix-boundary change answers for every spelling routing accepts. Key-level entries in mcp_tool_permissions and toolset rows name a tool on one server and dispatch compares them bare, so a wire-form entry advertised a tool that tools/call then refused. REST listing now goes through filter_tools_by_key_team_permissions, the same function the MCP list path uses.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-07-30 22:13:10 -07:00
..
test_configs
conftest.py
mcp_e2e_upstream_server.py
mcp_server.py
test_aresponses_api_with_mcp.py
test_mcp_auth_header_extraction.py
test_mcp_auth_priority.py
test_mcp_chat_completions.py
test_mcp_client_unit.py
test_mcp_guardrails.py
test_mcp_hooks.py
test_mcp_litellm_client.py
test_mcp_logging.py
test_mcp_server.py fix(mcp): keep REST tool listing in step with key/team grant enforcement 2026-07-30 22:13:10 -07:00
test_oauth2_mcp_config.yaml
test_openapi_spec_path_url.py
test_per_user_oauth_cache.py
test_proxy_mcp_e2e.py
test_semantic_tool_filter_e2e.py