MCP tools
Lattix MCP tools mapped to the public metadata-only Platform API.
The MCP server exposes all eight public /v1/sdk/* capabilities. Tool outputs
retain the Platform API response shape, including the resolved caller tenant
identity.
| Tool | Behavior | Platform API |
|---|---|---|
lattix_get_capabilities | Read active auth, domains, routes, and scope requirements | GET /v1/sdk/capabilities |
lattix_get_bootstrap | Read operations, profiles, and enforcement metadata | GET /v1/sdk/bootstrap |
lattix_whoami | Read the resolved tenant, principal, subject, and scopes | GET /v1/sdk/whoami |
lattix_get_protection_plan | Resolve local protect, access, or rewrap guidance | POST /v1/sdk/protection-plan |
lattix_resolve_policy | Resolve tenant policy from workload and resource metadata | POST /v1/sdk/policy-resolve |
lattix_get_key_access_plan | Resolve wrap, unwrap, or rewrap guidance without key material | POST /v1/sdk/key-access-plan |
lattix_register_artifact | Register metadata for an already-protected artifact | POST /v1/sdk/artifact-register |
lattix_record_evidence | Record metadata-only enforcement evidence | POST /v1/sdk/evidence |
Use Platform API endpoints for the authoritative field semantics. MCP schemas enforce bounded strings, arrays, attributes, and sizes before forwarding the same metadata contract.
Write confirmation
lattix_register_artifact and lattix_record_evidence change tenant state.
Under MCP 2026-07-28, the server returns an input request asking the user to
confirm before it executes the write. Clients must display that request and
return the confirmation through the protocol's input-response channel.
Legacy MCP 2025-11-25 clients cannot use that multi-round flow. After showing
the operation to the user, they repeat the call with confirmed: true.
Confirmation does not replace authorization. The tenant binding and all required scopes are checked again when the tool executes.
Data boundary
Send identifiers, labels, digests, sizes, locators, workload metadata, purpose, and policy attributes only. Do not send:
- plaintext document or message content;
- raw artifact bytes or base64 payloads;
- encryption keys or private keys;
- OAuth tokens, client secrets, or authentication headers;
- unnecessary personal or regulated data.