Bind the right identity
Organizational registration, OAuth client identity and the initiating actor have distinct roles. Tokens must target the intended resource and permitted scope.
Distinguish the user who initiated work from the service that executes it. Organizational registration, client identity and subject identity serve different purposes. A browser session and an MCP client call are also distinct access paths. Review the actual deployment contract instead of assuming one successful sign-in authorizes every interface.
- Bind client and subject to the reviewed registration.
- Recheck current roles and environment access.
- Deny dispatch when required identity cannot be established.
Review the exact operation
Approval should bind the destination, tool version, normalized arguments, artifact digests, budgets and expiry. Relevant changes invalidate that approval.
Approval is meaningful only in relation to a specific operation. Record the argument and artifact identities the reviewer saw, the intended destination, relevant limits and expiry. A later change to a material input should trigger a fresh evaluation of authority rather than silently inheriting the previous decision.
Identity and exact approval converge at dispatch
Establish the initiating subject and registered application.
- Separate the requester from the independent reviewer.
- Treat discovery metadata as information, not permission.
- Never use model output as an authority to expand access.
Retain the decision trail
A reviewable connection preserves both allowed and denied outcomes within its documented logging boundary.
Keep enough context to explain why an operation was allowed, denied or withheld while respecting the documented logging boundary. Retain actor and policy references and the relevant evidence identities. Avoid copying credentials or raw sensitive arguments into ordinary diagnostic output.
Can an approved synthetic fork be reused after its arguments change?
Record the original checkpoint and normalized arguments, then vary a material input in a controlled negative test. Inspect the authorization outcome and retained references.
The reviewer should verify that the old approval is not silently treated as authority for a different operation. Customer identity interoperability requires its own qualification.
- Keep secrets and raw sensitive arguments out of ordinary audit events.
- Retain policy, source and model references.
- Test suspension, expiry, revocation and control outages.
Separate discovery from permission
A client may discover that a tool exists without being allowed to invoke it on a particular object or environment. Treat tool descriptions, source labels and model-generated instructions as information, not as authority.
Use exact grants and current environment access to constrain the operation. Revocation, suspension and expiry matter at dispatch time. A past successful request is not evidence that the same request remains authorized today.
Different identities, different responsibilities
| Identity or record | Responsibility | Do not infer |
|---|---|---|
| Organizational registration | Defines reviewed trust context. | Permission for every tool or environment. |
| Client and initiating actor | Identify who is requesting work. | Approval for a sensitive operation. |
| Exact-action approval | Authorizes a specific operation within its limits. | Authority for changed arguments or expired scope. |
- Review current identity and environment scope.
- Keep tool discovery and invocation decisions distinct.
- Do not let model output broaden a grant.
Rehearse the control failures
A meaningful control review includes negative cases. Test expired approval, changed arguments, revoked registration and missing required identity or policy information using the supported internal contract.
Record the expected decision before the test and retain what actually happened. Customer identity-provider integration, credential management and operational acceptance remain deployment-specific, even when the internal control paths behave as designed.
Keep the evidence and its conditions together. A later success does not erase an earlier failure or broaden the original scope.
- Include denied and withheld cases in the review.
- Retain exact policy and operation references.
- Qualify customer identity and custody separately.
Prepare an authority review
Map each trust decision to an accountable owner: client registration, source approval, environment access and sensitive action approval. Keep the initiating actor and executing service visible through the review.
Use the checklist to describe the boundaries and test cases. It grants no permissions. Before a deployment, review the exact identity configuration and control behavior with the appropriate platform and customer owners.
Review preparation
0 / 6 prepared- Document who may request, review and execute.
- Pin the operation being approved.
- Record revocation and expiry behavior.