ISMS Copilot Docs

Tokens, scopes, and security

How pat-isms tokens work: scopes, revoke, expiry, and hard limits.

Inhalt auf Englisch

Diese Seite ist für diese Sprache noch nicht übersetzt. Unten siehst du die englische Version, bis die Übersetzung verfügbar ist.

Account tokens let an MCP client act as your user, limited by the scopes you selected when the token was created.

Prefix and lifecycle

StepBehaviour
CreateSettings → Connected apps → Create token
DisplayFull secret shown once; starts with pat-isms-
StoreClient config only; never commit to git
RevokeSame Settings page; takes effect immediately
ExpiryOptional at creation

Scopes (typical)

Exact labels in the UI may vary slightly; the intent is:

Account

CapabilityReadWrite / act
Account infoyesno
Workspaceslistno
Documentslist metadata only (no get-by-ID tool)no
Memoriesyescreate / edit when granted
Conversationsn/astart and send when granted

Model API (Connected apps group)

ScopePurpose
api_keys:readList sk-isms key metadata (no secrets)
api_keys:writeCreate / revoke sk-isms keys via MCP when the keys flag is on
api_credits:readRead prepaid API credit balance
api_credits:checkoutCreate a Stripe Checkout URL for top-up when the checkout flag is on

These scopes do not let a pat-isms call inference. The agent still uses a separate sk-isms key for api.ismscopilot.com. See Set up from Claude Code or Grok.

Grant the minimum set for the agent’s job. A read-only workspace token cannot start conversations.

Hard limits (by design)

  • Beyond is available when the agent passes mode: "beyond" (Fast is the default). Paid plans, 10 runs per UTC day. See Using Beyond mode.
  • Advanced Data Protection cannot be toggled via the token. The agent can report status; you change it in Settings → Data Protection.
  • Rate limits apply (on the order of ~120 requests/minute per token; concurrent conversations are capped per account). If you hit limits, back off and retry.
  • pat-isms alone does not run model-API completions. Model API tools (when enabled) mint sk-isms and open credit checkout; Embed partner billing stays separate.

Security checklist

  1. Name tokens by device or purpose (claude-laptop, cursor-ci).
  2. Prefer short expiry for temporary machines.
  3. Revoke when a laptop is lost or a CI secret rotates.
  4. Never put pat-isms-… in public repos, screenshots, or support tickets.

Usage counts against your normal chat subscription and plan limits, not against API prepaid credits.

Auf dieser Seite