Review a submission

Review the target, access boundary, and compatibility evidence before approval.

Before you start

Use a reviewer identity with permission over the submitted resource. Obtain the intended use case and owner context.

Procedure

1. Open the pending submission and compare the requested configuration with the stated use case.

2. Review endpoint, transport, route, discovered tools or selected API operations, and credential requirements.

3. Resolve validation and compatibility warnings. If the scope is wrong, return or reject the submission with a specific reason through the available review action.

4. Approve the eligible configuration, then hand the owner the remaining activation and runtime verification steps.

Verify the result

Check the resulting resource state and administrative audit record. Verify the approved revision is the one the runtime uses.

If it does not work

Approval is not a policy grant. If the caller still sees no tools, investigate the caller permissions and runtime state separately.

Read the related concept or consult the Admin API for exact request fields.

Implementation reference

Read the source contract.