You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2799d3c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): honour T3-Mode-Inherit only from a peer link
The independent re-reviews of b73f8fe found three gaps.
- The receiving /mcp accepted T3-Mode-Inherit from any OAuth client, so a
non-link client could start its own omitted-mode launch at its ceiling
rather than the project default. That widens no access, but it breaks
the rule that a client outside a thread keeps the local default.
- No test pinned that an inheriting launch takes the caller's own mode
rather than the link's access.
- No test pinned the receiver's header rules.
Changes:
- withModeLimit sets inheritsModes only for a linked client.
- PeerForwarding's launch test adds a thread whose mode (auto) sits
between the box default and the full-access link. It must start at
auto.
- McpHttpServer's T3-Mode-Limit test gains a peer-link caller and pins
four rules: inherit is honoured beside a valid limit; ignored without
one; ignored unless the value is "1"; ignored from a non-link client.
- The MODE_LIMIT_HEADER doc now says a broad limit gains no access,
rather than nothing.
- docs/internals/remote.md states the receiver rule and mixed-version
behaviour.
- docs/user/remote-access.md tells users what mode a linked task starts
in.
Fails before: with the linked check removed (b73f8fe's receiver), the
McpHttpServer T3-Mode-Limit test fails on the non-link row. After:
PeerForwarding 6/6 and the McpHttpServer T3-Mode-Limit test pass. tsc,
fmt and lint are clean on the changed files.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01A1D6J2UMPo7YBWQFvbg1br
0 commit comments