DOC Model Safety Gate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRATA_USER_ID | No | Older alias for DOCMODEL_USER_ID. Identity the server acts as (sent as the x-user-id header). | |
| DOCMODEL_USER_ID | No | Identity the server acts as (sent as the x-user-id header). | |
| STRATA_API_TOKEN | No | Older alias for DOCMODEL_API_TOKEN. Bearer token sent to the API. | |
| STRATA_USER_ROLE | No | Older alias for DOCMODEL_USER_ROLE. Role of the user: member (default) or admin. | member |
| STRATA_PROJECT_ID | No | Older alias for DOCMODEL_PROJECT_ID. Project the server is scoped to (sent as the x-project-id header). Required for member access, which is the default role. | |
| DOCMODEL_API_TOKEN | No | Bearer token sent to the API. | |
| DOCMODEL_USER_ROLE | No | Role of the user: member (default) or admin. | member |
| DOCMODEL_PROJECT_ID | No | Project the server is scoped to (sent as the x-project-id header). Required for member access, which is the default role. | |
| STRATA_API_ENDPOINT | No | Older alias for DOCMODEL_API_ENDPOINT. GraphQL endpoint of the Safety Gate API, e.g. http://localhost:4001/graphql. | |
| DOCMODEL_API_ENDPOINT | No | GraphQL endpoint of the Safety Gate API, e.g. http://localhost:4001/graphql. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listWorkflowsA | List workflow definitions for a project, optionally filtered to one site. |
| getWorkflowC | Get one workflow definition by ID. |
| createWorkflowA | Create a workflow definition (the step-based editor path). The API requires at least one step: pass steps as an array of { position, stepType, configJson, isEnabled? }. For graph-based workflows, create the definition here, then add nodes and edges with the graph tools. |
| runWorkflowC | Run a workflow in DRY_RUN or LIVE mode |
| getRunStatusC | Get the status and details of a workflow run |
| listWorkflowNodesC | List all nodes in a workflow graph |
| createWorkflowNodeC | Add a node to a workflow graph |
| createWorkflowEdgeC | Connect two nodes with an edge |
| getNodeRunsB | Get node-level run results for a workflow run |
| listPendingReviewsA | List workflow runs whose AI outputs are waiting for human review in the Safety Gate, with a pending count for each. Nothing in these runs has been published. |
| getGateReviewA | Get every AI output waiting in the Safety Gate for one run, field by field: the original value, the AI's proposed value, and its review status (pending, accepted, rejected, edited). This is the diff a human reviews before anything can go live. |
| reviewOutputA | Record a human review decision for one AI output in the Safety Gate: accepted, rejected, or edited. When the action is edited, pass editedValue with the corrected value. Reviewing never publishes anything by itself; a run can only go LIVE after every output is reviewed. |
| bulkReviewOutputsA | Accept or reject every pending AI output in a run at once. Returns how many outputs were reviewed. Bulk review does not support edited; review edited outputs one at a time with reviewOutput. |
| publishReviewedRunA | Publish a reviewed run: runs the workflow LIVE using the outputs a human accepted or edited in the Safety Gate. The API refuses a LIVE run when any AI output is still pending or rejected, so an unreviewed change cannot be published through this tool. |
| rollbackRunC | Roll back a workflow run, reversing what it published. |
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 15 tools
Most tools map cleanly to a resource+action, and the review tools (listPendingReviews vs getGateReview, reviewOutput vs bulkReviewOutputs) are well separated by granularity. Minor overlap remains between runWorkflow in LIVE mode and publishReviewedRun, and between getRunStatus and getNodeRuns, where an agent must reason about which is authoritative.
All 15 tools use camelCase with a verb-first pattern (list/get/create/run/review/publish/rollback + noun), including predictable variants like reviewOutput vs bulkReviewOutputs and listWorkflows vs listWorkflowNodes. No mixed conventions or stray vague verbs.
15 tools is at the upper edge of the well-scoped band, but it covers two genuine sub-domains (workflow authoring/execution and the Safety Gate review lifecycle). Each tool has a defensible role, though the graph node/edge tools add weight for what may be an occasional editing path.
Read/create/run/review/publish/rollback are covered well, but the surface is asymmetric: workflows and graph nodes/edges can be created yet there is no updateWorkflow, deleteWorkflow, deleteWorkflowNode, or deleteWorkflowEdge, leaving dead ends in graph editing. There is also no way to list all runs for a workflow, only run-specific status lookups.