atlasent-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASENT_MODE | No | local = offline rules engine; remote = hosted API. | |
| ATLASENT_API_KEY | No | AtlaSent API key. Leave empty for offline local mode. | |
| ATLASENT_BASE_URL | No | AtlaSent API base URL (ends in /functions/v1). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evaluateA | Call this BEFORE performing any sensitive action. Returns a Decision: |
| verify_permitA | Call this AFTER |
| deploy_serviceA | Example protected tool. Every call is authorized AND its Permit is verified by AtlaSent before the deploy runs. Denied, held, expired, replayed, mismatched, or unverifiable calls are blocked and never touch the target system. |
| atlasent_evaluateA | Evaluate an action against your published AtlaSent policies. Returns allow/deny/hold/escalate with a permitToken on allow. Use this when ATLASENT_MODE=remote and you need to gate an action against your hosted policy engine. |
| atlasent_list_policiesA | List all constraint bundles / policies for this organization. |
| atlasent_get_policyA | Retrieve a single constraint bundle / policy by ID. |
| atlasent_list_audit_eventsB | Retrieve recent evaluation events from the audit log. |
| atlasent_explain_authorityA | Explain why a principal currently has (or lacks) authority for a scope. Answers 'why may principal P exercise scope/action A in organization O right now?' — strictly read-only, does not change /v1-evaluate, /v1-verify-permit, or any deny/hold/allow semantics; it explains the same facts those paths already read. Every matched authority mechanism (direct_grant, delegation, role_capability) is reported as its own path entry; every excluded or ambiguous relationship is reported as its own unresolved finding. |
| atlasent_integrity_auditA | Audit the organization's authority graph for internal inconsistency and return the report verbatim. Strictly read-only; changes no policy, permit, or decision. THIS IS NOT A PASS/FAIL HEALTH CHECK and the tool synthesizes no verdict of its own. Each finding carries a three-way |
| atlasent_create_policyA | Create a new constraint bundle for an action. The bundle starts in 'draft' status — call update_policy to publish it. |
| atlasent_update_policyA | Update a constraint bundle — change rules, title, or publish/archive it. Only fields you provide are updated; omitted fields are unchanged. |
| atlasent_delete_policyA | Permanently delete a constraint bundle. Prefer archiving over deleting. |
| atlasent_revoke_permitA | Revoke a permit before it expires. The permit immediately becomes invalid for verify_permit calls. |
| atlasent_list_permitsA | List issued permit tokens for audit and monitoring. |
| atlasent_get_permitA | Fetch one permit's record: status, actor, action, environment, issue/expiry/consume times and the decision that issued it. Never returns the permit token itself. |
| atlasent_check_permitA | Check whether a permit is still usable without consuming it. Returns { valid, status } where status is active, revoked, consumed or expired. Use before a deferred action to avoid acting on a permit that was revoked meanwhile. This is a status read, not authorization: execute only after atlasent_verify_permit. |
| atlasent_get_decisionA | Fetch one authorization decision (execution evaluation) by id: the decision, deny code, actor, action, context and evidence fields. Set include_trace to also return its approval events, permit uses and webhook deliveries. Requires audit:read. |
| atlasent_permitA | Manually issue a permit token for an action. Use for pre-authorized operations where a full evaluate call is not practical. |
| atlasent_verify_permitA | Verify a permit token with full binding inputs against the V1 endpoint. Use this at the execution boundary before the governed native effect; under-specified verification is a bypass vector. |
| atlasent_create_approval_requestA | Create an approval request for a held action. The request ID is returned in the evaluate response when decision is 'hold'. Submit resolution via atlasent_resolve_approval_request. Approval is an input to Authorization; it does not itself authorize or prove execution. |
| atlasent_resolve_approval_requestA | Approve or deny a pending approval request. Approval records a verified input; the protected action must still satisfy the current authorization/reevaluation path and Permit Verification before execution. |
| atlasent_record_execution_evaluationA | Record the outcome of an execution that was permitted by a prior evaluate call. Closes the evidence loop with the observed execution result; it does not replace pre-execution Permit Verification. |
| atlasent_create_webhookA | Register a webhook URL to receive evaluation events. |
| atlasent_delete_webhookB | Remove a registered webhook. |
| atlasent_lookup_actionA | Look up canonical action specifications from the Authorization Intelligence Library. Returns the permanent canon_id, gate flags (requires_human_approval, requires_mfa, requires_verified_actor, requires_state_snapshot), authorization pattern, risk posture, AI risk classification, regulatory mappings, evidence requirements, and the action's knowledge-graph relationships (what it requires and produces, and which frameworks / control objectives it satisfies) for every governed action type in the Canon. Use |
| atlasent_atlas_lookupA | Look up a canonical AtlaSent concept from the Knowledge Atlas — the compiled graph of the system's own vocabulary (Caller, Authority, Policy, Decision, Permit, Verification, Evidence, Audit Chain, Gate, Trust Root, ...). Returns the concept's canonical definition (its source-of-truth doc), its relationships (what it depends on and what depends on it), the surfaces that realize it, and its ADR / API / SDK / implementation anchors — so every AI host reasons from the same canonical knowledge instead of guessing. Use |
| atlasent_evaluate_manyA | Evaluate up to 100 actions in a single request against your published AtlaSent policies. Returns decisions in input order. Optional batch_id (UUID) provides idempotency. Closed-by-default: 404 surfaces as a |
| atlasent_evaluate_streamA | Evaluate up to 100 actions via the streaming endpoint. The tool buffers the SSE stream and returns the complete result set (same shape as atlasent_evaluate_many). Per-item RPC failures surface in the items array with |
| atlasent_queryA | Run a read-only GraphQL query against the AtlaSent V2 GraphQL endpoint. Wave A schema: |
| atlasent_list_scim_usersA | List provisioned users via SCIM 2.0 (RFC 7643) for an organization. Supports filter expressions (e.g. 'userName eq "alice"') and startIndex/count pagination. |
| atlasent_get_scim_userA | Retrieve a single provisioned SCIM user by ID. |
| atlasent_create_scim_userA | Provision a new user via SCIM 2.0. Adds the user to the AtlaSent directory and makes them available for policy evaluation. |
| atlasent_patch_scim_userA | Update a provisioned user using RFC 7644 SCIM PatchOp operations. Each operation has op (add/remove/replace), an optional path, and a value. |
| atlasent_delete_scim_userA | Deprovision a SCIM user. Removes them from the AtlaSent directory. This is irreversible — prefer disabling (patch active=false) over deleting. |
| atlasent_list_scim_groupsB | List provisioned groups via SCIM 2.0 for an organization. |
| atlasent_get_siem_configA | Retrieve the SIEM export configuration for an organization. Enterprise plan required. The credential field is never returned. |
| atlasent_upsert_siem_configA | Create or update the SIEM export configuration for an organization. Enterprise plan required. destinationUrl must be HTTPS. The credential field is stored securely and never returned by GET. |
| atlasent_test_siem_deliveryA | Send a test event to the configured SIEM destination and report the result. Returns { success, statusCode, durationMs, error? }. Returns 409 if SIEM is not configured or is disabled. |
| atlasent_list_evidence_exportsA | List compliance evidence bundles for an organization. Enterprise plan required. Each record includes status and SHA-256 hash. |
| atlasent_get_evidence_exportA | Retrieve a specific compliance evidence bundle by ID. Includes status, SHA-256 hash for tamper verification, and download URL when complete. |
| atlasent_create_evidence_exportA | Generate a compliance evidence bundle for audit regimes (SOC 2 Type II, HIPAA, GDPR). Enterprise plan required. Returns SHA-256 for tamper verification. Default window is the past 90 days; use date_from/date_to to narrow it. |
| atlasent_vqp_generateB | Score a constraint bundle against the 6 VQP criteria (access_control CC6.1, audit_coverage CC7.2, escalation_paths CC7.4, deny_specificity CC8.1, hold_conditions CC6.3, override_governance CC5.2). Stores a tamper-evident snapshot with a SHA-256 prompt_hash in vqp_snapshots. Verdicts: qualified (≥85, no fails), conditionally_qualified (≥60), not_qualified. Requires ATLASENT_SUPABASE_URL and ATLASENT_SUPABASE_SERVICE_ROLE_KEY. |
| atlasent_vqp_verifyA | Re-derive the VQP prompt from current bundle data and verify it matches the stored SHA-256 prompt_hash. Detects tampering (hash_match: false) and optionally re-runs the AI model to detect score drift (score_delta, verdict_changed). Writes a vqp_audit_log row for SOC 2 CC7.2 / 21 CFR Part 11 evidence. Requires ATLASENT_SUPABASE_URL and ATLASENT_SUPABASE_SERVICE_ROLE_KEY. |
| atlasent_vqp_audit_summaryA | Retrieve a summary of VQP audit activity — hash match rates, drift event counts, and verdict changes — from the BCCAE compliance report. Use for SOC 2 evidence collection and monitoring dashboards. |
| atlasent_vqp_drift_eventsA | List VQP snapshots where the re-run AI score drifted by ≥10 points or the verdict changed (e.g. qualified → not_qualified). Use for compliance investigation and QA-VQP-002 § 7 deviation reporting. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 45 tools
The set contains near-duplicate entry points (evaluate/atlasent_evaluate, verify_permit/atlasent_verify_permit) that are hard to distinguish, and several permit-related tools (get/check/verify/permit) overlap in semantics. Many other tools are distinct, but the duplicates create real misselection risk.
Most tools follow an atlasent_<verb>_<noun> pattern, but the pattern is broken by unprefixed evaluate, verify_permit, and deploy_service, plus generic names like atlasent_query and atlasent_permit. Still readable and mostly snake_case, so not chaotic.
45 tools is far above the well-scoped range, and several are redundant (duplicate evaluate/verify) or a demo (deploy_service). A leaner set could cover the same platform with fewer entry points.
Core policy/permit/decision workflows are well covered, but subdomains have gaps: SCIM groups are read-only, webhooks have create/delete but no list/get, and SIEM config has no delete. These are workable but notable omissions for an admin surface.