Docs · AI agent signing

LK Approvals

When a policy rule uses Require approval for an AI agent, approvers decide in the LK Approvals web app — not in Console. Policy is still configured in Console; this app is the decision inbox only.

URL and install

Open https://console.liminalkeys.com/approvals/ on a phone or desktop browser.

  1. Sign in with your Liminal Keys account (same identity as Console) when you are listed as an approver on the rule.
  2. Use the browser Install / Add to Home Screen action to install the PWA.
  3. Allow web push notifications when prompted so new requests surface outside the app.
  4. The installed app refreshes sign-in in the background while it is open and re-registers web push when you return to it, after a service worker update, or on a weekly cadence — so alerts and the session stay healthy without signing in again until your organization's refresh lifetime ends.

Who can approve

Only users listed as approvers on the applied AI agent policy rule receive requests. If you are not on the rule, the inbox stays empty.

What approvers see

  • Agent-supplied document label
  • Up to three small preview images (agent-rendered, not verified against the digest)
  • Truncated DigestHashHex (full 64-character SHA-256 hash is stored server-side)

Preview images may be PNG, JPEG, or WebP. The API does not receive the full document—only the digest—so page thumbnails must come from the agent (for example pdftoppm) or from a server metadata fallback when the agent sent only a blank grey placeholder.

Timeout and MCP polling

MCP sign_hash waits up to 120 seconds by default (poll_timeout_seconds). If approvers have not acted, the tool returns pending_approval with an approval_id. The agent must call sign_hash again with the same client_nonce and that approval_id until the decision is signed or denied.

← AI agents & MCP