sayan-oai 0585dcb5db Preserve sandbox context in prepared MCP calls (#59020) ...

## Why

MCP permission profiles need the directory context used to interpret them. Prepared calls must retain that context alongside their captured permissions across runtime refreshes.

## What changed

- Store each server's permission source as thread permissions or a captured environment `FileSystemSandboxContext`.
- Capture environment working directories, home and temporary directories, and materialized workspace roots. Retain the host working directory for thread permissions.
- Expose the captured source through `PreparedMcpCall::permission_source()`, while keeping hosted Apps on thread permissions even when a local environment is attached.

## Testing

Extend binding tests to verify that prepared calls retain environment sandbox paths across refreshes and expose the host working directory for thread permissions. Update elicitation coverage to include hosted Apps with an attached local environment.

GitOrigin-RevId: 87e94605daece324786eebc07b62a507d35e5ced

2026-11-03 01:08:08 +00:00

..

auth.rs

Avoid blocking EMA auth status checks on account refresh (#56127)

2026-10-22 09:37:28 +00:00

mod_tests.rs

Preserve sandbox context in prepared MCP calls (#59020)

2026-11-03 01:08:08 +00:00

mod.rs

Preserve sandbox context in prepared MCP calls (#59020)

2026-11-03 01:08:08 +00:00