Best practice for scoping a FunctionTool to a single resource id?

[juanzahi]

I'm building a custom FunctionTool for my own ADK agent and want to follow best practice for scoping its permissions to a single resource. Some of the GitHub sample agents in this repo (e.g. the issue triaging one) bind a tool's write access to a single issue/PR number chosen by the workflow, rather than trusting whatever id the model passes in. Is there a built-in ADK primitive for that kind of per-call authorization binding, or is implementing an allowlist set (like AUTHORIZED_ISSUES in the Java samples) the recommended pattern for FunctionTools that take a resource id?

Thanks in advance!

[juanzahi]

@adk-bot could you take a look at this one, please?