Review & approve a submission

Approval is what turns a submission into live, callable configuration. Until a reviewer approves it, a registered server is inert.

Requires registry_reviewer (or equivalent)

Reviewing and approving submissions requires submission‑review permission in the target environment.

1. Open the approvals queue and pick a pending submission.
2. Compare the pending manifest to what’s live to see exactly what changes.
3. Approve or reject — approval compiles the server into the projection.

Review the submission

Open the approvals queue and review a submission

UIAPICLI

1. Open Govern → Approvals.
2. Select a pending row, then review the pending‑vs‑live comparison for the manifest.

GET/v1/approvals

Copy

curl "$GATEWAY/v1/approvals?environment_id=prod" \
-H "authorization: Bearer $TOKEN"

View listApprovalsQueue in the API reference →

Copy

gatewayctl status deployment --format json

There's no gatewayctl approvals verb yet — review and approve via the UI or the API below.

Approve or reject

Record an approval decision

UIAPICLI

1. From the submission, choose Approve or Reject and add a reason.
2. On approval the server is projected to the data plane and becomes callable per policy.

POST/v1/mcp-servers/{server_id}/submissions/{submission_id}/review

Copy

curl -X POST \
"$GATEWAY/v1/mcp-servers/legal-contract-review/submissions/sub_123/review" \
-H "authorization: Bearer $TOKEN" \
-H "content-type: application/json" \
--data '{"decision": "approve", "reason_code": "meets_policy"}'

View reviewMcpServerSubmission in the API reference →

Copy

gatewayctl explain

Approval is API/UI only today — POST .../submissions/{id}/review, or batch-approve via POST /v1/approvals/batch.

Batch where it's safe

The approvals queue supports batch decisions (POST /v1/approvals/batch) for clearing a backlog of low‑risk submissions in one action.