No secrets in the customer surface
No privileged backend credentials or private infrastructure identifiers appear in any customer-facing page or response.
Security posture / customer surface
Customer accounts are scoped, revocable, and observable from inside the account. The platform never exposes direct infrastructure access, privileged credentials, or private infrastructure identifiers to a customer session.
Control principles
No privileged backend credentials or private infrastructure identifiers appear in any customer-facing page or response.
Each customer account receives credentials scoped to the customer-safe tool surface. Scope is bound by the plan, entitlement policy, and organisation.
MCP credentials issued from inside the customer account are shown once at creation. Only a one-way hash is stored. Tokens are revocable at any time.
OAuth 2.1 connections to AI agent hosts can be revoked from inside the customer account. Revocation is enforced before the next tool call.
Plan-level rate limits and per-tool-family quotas are enforced by the Island Intel JA gateway, not by the identity provider.
Every customer tool call, allowed or denied, is recorded in an append-only telemetry stream the customer can review from inside the account.
Privileged credentials are never exposed to customer sessions, AI agent hosts, or any customer-facing surface.
The MCP tool surface visible to a customer's AI agent is restricted to the customer-safe profile. Operations tools and write paths are not reachable.
Telemetry records what tool ran, who called it, and which plan applied. It does not store raw client IP addresses or unnecessary PII.
Security researchers can report potential issues through the contact path provided to approved accounts. Do not publish or test against production resources without explicit authorisation.