Enforcement requires your runtime to call
evaluate before dispatch and honor the result. Unconnected tool paths are not automatically covered.Prerequisites
- Node.js 18 or later
SECTOR8_API_KEYSECTOR8_CLIENT_ID- A runtime path where you can block dispatch and fail closed on errors
Install the SDK
https://github.com/sector8-ai/sector8-sdk-typescript
Set your credentials
Evaluate before dispatch
REST
/api/v1/evaluate responses use the field decision. This SDK exposes the same value as outcome. Check for ALLOW the same way either way.
See Evaluate for the shared
ALLOW | DENY contract and Non-MCP integration for custom runtime wiring.
Optional: send telemetry
Telemetry records what happened. It does not replace evaluate-before-dispatch.Verify the integration
- Check health:
- Confirm an
evaluatecall returns a decision artifact - Confirm your runtime dispatches only on
ALLOWand fails closed on unknown/error - Optionally confirm telemetry appears in Sector8 if you send it
You are done when your TypeScript runtime evaluates before dispatch, blocks on
DENY, and fails closed on missing/unknown/error responses.Common mistakes
- Logging telemetry without calling
evaluatebefore tool dispatch - Treating
testConnection()as proof of enforcement - Dispatching on any non-error response instead of checking
decision.outcome === 'ALLOW' - Missing
SECTOR8_CLIENT_ID - Using the wrong host instead of
https://sdkapi.sector8.ai
