[FEATURE] Document a fixed per-session native-operation ceiling for subscription MCP integrations
Preflight
I searched existing issues, including #101426. This is one request for a documented, fixed per-session authority ceiling; it is not a request to bypass managed organization policy.
Problem statement
We are building a subscription-backed integration using unmodified Claude Code. Our pinned source examination is of 2.1.296; we have not qualified a live Claude session. The design separates the native credential zone from repository workers and exposes a fixed host-owned MCP callback catalog.
We need to know whether a supported launch recipe can establish the maximum permitted native operations before account-dependent startup helpers run and keep that ceiling enforced throughout a turn. Empty built-in tool settings and strict MCP configuration are useful, but our examination has not established this complete lifetime property. Conditional source paths are not evidence that any particular account exercised them.
Proposed solution / question
Please document the supported controls, if they exist, for:
- a fixed, explicitly qualified authentication/refresh startup-helper set;
- an exact host-owned MCP catalog and no additional model-selectable operations;
- later policy/plugin/configuration changes being unable to widen that ceiling;
- supported pre-model subscription-mode and effective-configuration observations.
If mandatory organization policy conflicts with the requested ceiling, failing closed is acceptable and preferred. We are not asking to override, disable, or evade that policy. If some part is unsupported, identifying the missing capability would let us keep the integration unavailable honestly.
Alternatives
Keep the integration unavailable pending supported controls. We are not proposing a patched vendor binary, credential interception, or inferred success from an empty tool listing.
Use case
An operator-attended software-maintenance workflow with direct subscription login and separately contained repository workers. Related #101426 concerns preserving explicitly configured MCP in safe mode; this request additionally concerns startup and lifetime enforcement.
Priority / category
High for our integration; CLI configuration / SDK interoperability.
Public integration context: https://github.com/sushiHex/constructicon/issues/175