Skip to content

feat(google_adk): add ADK-111, MCPToolset with no tool_filter - #51

Merged
ivanpaghubasan merged 1 commit into
mainfrom
feat/tool-allowlist-detection
Aug 25, 2026
Merged

feat(google_adk): add ADK-111, MCPToolset with no tool_filter#51
ivanpaghubasan merged 1 commit into
mainfrom
feat/tool-allowlist-detection

Conversation

@ivanpaghubasan

Copy link
Copy Markdown
Collaborator

Closes Class 2 of the tool access-control detection scoping — Google ADK genuinely has a 'true restriction' semantic (unlike Claude/OpenAI's permission-style allow-lists), making 'no explicit filter' the correct risk signal.

MCPToolset connects an agent to a remote MCP server's entire tool catalog, which is not enumerable from source and can change whenever the server updates. tool_filter= is the only mechanism narrowing that catalog to a named allow-list.

Mirrored byte-for-byte from the engine fixture (verified via diff, no output — fully in sync).

Closes Class 2 of the tool access-control detection scoping —
Google ADK genuinely has a 'true restriction' semantic (unlike
Claude/OpenAI's permission-style allow-lists), making 'no
explicit filter' the correct risk signal.

MCPToolset connects an agent to a remote MCP server's entire
tool catalog, which is not enumerable from source and can
change whenever the server updates. tool_filter= is the only
mechanism narrowing that catalog to a named allow-list.

Mirrored byte-for-byte from the engine fixture (verified via
diff, no output — fully in sync).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant