Airlock
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRLOCK_BUCKET_DENYLIST | No | Comma-separated list of your org's infrastructure names (bucket names, hostnames) to redact. Empty by default. |
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 |
|---|---|
| submit_storyA | Submit a war story. Validated against the AgentPier schema and run through the safety gate on ingest. Rejected with findings if any sensitive data is detected (account IDs, IPs, ARNs, secrets, denylist buckets, PII). Returns the story id on success. |
| search_storiesA | Search war stories by keyword and/or tag. All results are scrubbed on egress (defense-in-depth). Returns a list of matching stories. |
| get_storyA | Fetch a single war story by UUID. Scrubbed on egress. |
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 3 tools
Each tool has a clearly distinct purpose: get_story fetches by UUID, search_stories searches by keyword/tag, and submit_story creates a new story. No functional overlap exists.
All tools follow a consistent verb_noun pattern in snake_case: get_story, search_stories, submit_story. No deviations or mixed conventions.
Three tools form a minimal but complete set for the server's purpose: submitting, fetching individually, and searching. The count is well-scoped for a focused narrative storage system.
Covers create, read, and search operations. Missing update and delete, which may be intentional given security constraints (scrubbed on egress). Minor gap that agents can work around.