Quick overview
This workflow accepts authorization requests via webhook or manual runs, evaluates them using hierarchical policy inheritance and zero-trust context checks, returns an allow/deny decision, and optionally sends a WhatsApp alert for human review.
How it works
- Receives an authorization request via an HTTP POST webhook (or a manual test trigger) and normalizes the payload into a consistent request structure.
- Validates that the request includes principal, action, and resource fields, and immediately returns a 400 response if the payload is invalid.
- Loads governance configuration such as inheritance depth, zero-trust strictness, risk thresholds, and audit/review settings.
- Resolves the principal’s organization/team hierarchy and collects inherited and override policies into a merged policy set.
- Evaluates the request against the merged policies and zero-trust requirements (for example purpose, device posture, and risk score) to produce an allow/deny effect with detailed reasons.
- Builds the final decision and audit record, responds to the webhook caller with the decision object, and sends a WhatsApp message if the decision requires human review.
Setup
- Configure the Webhook trigger URL in the calling system by copying the production webhook URL for the
mcp-authorize endpoint.
- Add WhatsApp Business credentials for the WhatsApp node and set the WhatsApp Phone Number ID and recipient phone number in the governance configuration.
- Review and update the governance configuration values (inheritanceDepth, zeroTrustStrictness, requirePurpose, maxRiskScore, and humanReviewRiskThreshold) to match your security posture.
- Replace the inline, simulated hierarchy and policy lookup logic with your real identity directory and policy source if you need production policy data.