jif 65f8bf6853 Bind MCP calls to captured catalog revisions (#34588) ...

## Why

An MCP connection or tool catalog can change after a model step captures its
available tools. Calls from that step must not be rerouted to a replacement
client or run against a catalog revision the model did not see.

## What changed

- Add `McpBinding` to capture the ready clients, visible tools, resources, and
  server metadata for one sampling request.
- Prepare calls against the captured client and reject them if the tool catalog
  changes before call preparation and execution finish.
- Keep resource access and cache identity tied to the binding's exact connection
  set, and omit servers that do not have a ready client.
- Preserve each client's unfiltered tool catalog so bindings can apply the
  current filter consistently.

## Testing

Add coverage for connection replacement, stale catalog rejection, serialized
call preparation and refresh, ready-client capture, and binding-scoped resource
identity.

GitOrigin-RevId: a25da4d2c7f5ed06c41caa0c6d15c464c1698314

2026-07-21 18:13:41 +00:00

..

src

Bind MCP calls to captured catalog revisions (#34588)

2026-07-21 18:13:41 +00:00

BUILD.bazel

Extract MCP into codex-mcp crate (#15919)

2026-04-01 19:03:26 -07:00

Cargo.toml

Reuse MCP tool catalogs across sessions (#33184)

2026-07-14 22:25:39 +00:00