Tool visibility should respect session permission filters across runtime and experimental endpoints

Problem

Tool visibility can drift from enforceable permissions:

runtime may advertise tools that are denied by session-level permission rules
/experimental/tool and /experimental/tool/ids can list tools without applying agent/session permission context
generated SDK query types did not expose the optional permission-context fields

Tool lists shown to models and API clients should only include tools that are actually invokable under merged agent + session permissions.

runtime LLM tool filtering path
experimental tool listing endpoints
generated SDK query contract for optional provider, model, agent, sessionID

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

No issue template was used. Please resubmit using one of the three required templates: Bug Report, Feature Request (title must start with [FEATURE]:), or Question. Each template has required fields that must be filled in.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

This issue might be a duplicate of existing issues. Please check:

sdk.prompt({ tools }) does not override agent configured permissions #17063: sdk.prompt({ tools }) does not override agent configured permissions — overlaps with the SDK permission-context filtering scope described here.

If you believe this was flagged incorrectly, please let a maintainer know.

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.