Directory / Google ADK
Google ADK
Tool confirmation can pause a call for a yes or no, and before-tool callbacks can block calls that break policy. Sandboxing and network perimeters are left to you.
Lock this down first
Add a before_tool_callback that validates arguments, and use a sandboxed code executor rather than local execution.
Scorecard
| Criterion | Rating | Notes |
|---|---|---|
| Permission granularity | 2/3 | Before-tool callbacks and in-tool policy checks can block calls. |
| Human approval gates | 2/3 | require_confirmation pauses a tool for approval. The feature is marked experimental. |
| Sandboxing | Unverified | Not confirmed in the docs we checked. |
| Secrets handling | Unverified | Not confirmed in the docs we checked. |
| Audit logs | 2/3 | Python logging plus OpenTelemetry GenAI logs. Logging plugins capture tool calls. |
| Kill switch / interrupt | Unverified | Not confirmed in the docs we checked. |
| Network egress control | 0/3 | Docs advise confining agents inside VPC Service Controls perimeters, a Google Cloud control you set up yourself. ADK itself provides none. |
Sources
Vendor? Request a correction. We review corrections within 7 days.
