How do I review a LlamaIndex custom ClientSession authorization boundary?
LlamaIndex documents custom ClientSession integration, but it is an extension point rather than a shortcut around protocol initialization or account authorization. Review how the application supplies approved access before using a custom session for Montage tool discovery or execution. A custom session needs a clear application-owned responsibility and a version-matched extension point. It must preserve initialization and account boundaries rather than becoming a shortcut that makes raw HTTP reachability look like an authorized workspace call.
Help me review a LlamaIndex custom ClientSession authorization boundary. Locate the application’s ClientSession customization and its intended responsibility. Inspect the real workspace or failure and record which session path produced it. No writes.Identify why a custom session exists
Locate the application’s ClientSession customization and its intended responsibility. Determine whether it handles transport, approved auth or another concern instead of attributing every remote failure to the server. A clear customization rationale prevents an auth extension from accidentally becoming a bypass of the SDK’s initialization or result-handling responsibilities.
Match the installed extension point
Consult the version-specific LlamaIndex MCP documentation for session injection. Do not import constructor assumptions from another framework or bypass initialization because an ordinary HTTP request appeared to work. Use the installed integration’s documented injection interface rather than guessing that every ClientSession class from another MCP package fits this extension point.
Keep account state private
Review how the session associates approved authorization with the requesting user. Notebook outputs, tool descriptions and model arguments must not become token storage or expose another user’s client state. Private storage should remain outside notebook outputs, even if a debug print seems useful for confirming which configured client the application constructed.
Validate through the actual session
Use the configured session to execute signals_status directly, not a separate client that happens to work. A successful parallel path cannot prove the custom session’s authorization and lifecycle are correct. The status call must use the customized session under investigation; a second standalone client’s success would leave the original integration boundary unverified.
Retain exact evidence
Inspect the real workspace or failure and record which session path produced it. Unsupported auth remains a blocker rather than justification to return synthetic status or broaden the application’s permissions. A blocked custom session should stay blocked in the handoff, with no synthetic result or borrowed account path presented as evidence that the customization worked.
Keep the boundaries clear.
- Private storage should remain outside notebook outputs, even if a debug print seems useful for confirming which configured client the application constructed.
- A blocked custom session should stay blocked in the handoff, with no synthetic result or borrowed account path presented as evidence that the customization worked.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.