Read-only by design
Every Encrisoft MCP tool is read-only and side-effect free. No tool writes data, sends messages, launches simulations or exports records, so text in a result cannot trigger an action in Encrisoft.
Tenant isolation
- Each installation belongs to one organisation, and every result comes from that organisation only.
- No tool accepts an organisation identifier, and unknown arguments are rejected.
Data minimisation
Data is minimised inside Encrisoft before it leaves, and the MCP server strips anything outside each tool’s output schema.
- No personal data: no employee names, avatars, email addresses, employee identifiers, “top risk users” or recent activity.
- No plan, subscription, seat or billing details.
- Risk is aggregated. A department is included only when at least 5 of its employees have an actual risk score, and at most 10 departments are returned.
- The training catalogue contains only published courses.
Untrusted content and prompt injection
Organisation names, department names and course titles and descriptions are written by people in the organisation. Encrisoft returns them as data: control and bidirectional-override characters are removed, whitespace is collapsed and lengths are bounded (names 120, titles 160, descriptions 600 and categories 60 characters). Text results start with a notice that this content is data, not instructions.
Token security
- Access tokens are bound to the Encrisoft MCP resource and to one installation. Their default lifetime is 10 minutes, and they never outlive the installation.
- The MCP server never forwards your token. It exchanges it for an internal token that lasts at most 2 minutes.
- Authorisation is re-checked on every call, so revocation and permission changes apply immediately.
Transport protections
- HTTPS only, with an allow-list of host names.
- Request bodies are limited to 64 KB.
- Tokens are accepted only in the
Authorizationheader, never in URLs, and responses are not cached.
Auditing
Encrisoft records token issuance and every tool call with its outcome (success, denied, rate-limited or error), correlation ID and duration. Result content is not recorded. Creating and revoking an installation is recorded in the organisation’s audit log.
Partner responsibilities
- Keep client secrets in a secret manager and use Encrisoft MCP only from your servers.
- Request only the scopes you need.
- Do not log tokens or secrets, and handle results according to your agreement with Encrisoft and the customer.
- Report suspected credential exposure to Encrisoft immediately.

