dome guards manages Guards — content-inspection definitions that redact, omit, or block governed traffic. A Filter is a workspace-scoped, versioned Guard bound to a connection’s ordered chain per direction. Text Filters attach to model connections; JSON Filters attach to MCP server (tool) connections.
Editing a Filter deploys a new active version. Assigned connections pick it up on the next gateway sync — history is preserved and can be rolled back to.
Filter kinds
A Filter’s kind is structural and immutable at create time.
Both kinds enforce fail-closed: a Filter whose stored config fails to decode blocks that
(connection, direction) until the config is fixed. The gateway never relays unfiltered traffic.
Filters list
dome guards filters list
List the workspace’s Filters, showing each one’s active version and a compact config summary (e.g. redact[substring:"foo", ssn]; block[substring:"bar"] or omit[ssn, dob]; redact[email]).
Filters get
dome guards filters get <name-or-id>
Show a single Filter’s active version and config.
Filters versions
dome guards filters versions <name-or-id>
List the Filter’s version history (newest first). Rollback-produced versions cite the source version id.
Filters create
dome guards filters create <name>
Create a Filter — its first active version.
The convenience flags build at most two components — a
redact component and a block component, redact ordered first — and only produce text Filters. Use --config-from to author a JSON Filter or a multi-component text chain.
JSON Filter config example
tool-scrub.json
BLOCK withholds the whole message. OMIT removes the key and value. REDACT rewrites the value with a redaction sentinel. When multiple actions target the same key, BLOCK > OMIT > REDACT.
Filters update
dome guards filters update <name-or-id>
Edit metadata in place, or deploy a new active version by passing any config flag. The old version is preserved in history and assigned connections follow the active version on the next gateway sync.
Pass at least one of name, description, or a config flag.
Filters rollback
dome guards filters rollback <name-or-id> --to-version <n>
Roll a Filter back to an earlier version. The target version’s config is copied forward into a new active version — history is never mutated.
Filters delete
dome guards filters delete <name-or-id>
Hard-delete a Filter and its connection assignments. Corrupt Filters can still be addressed by UUID even when their config fails to render.
Model guards filters list
dome model guards filters list <connection>
List the text Filters assigned to a model connection, in chain order, grouped by direction.
Model guards filters set
dome model guards filters set <connection>
Replace the entire ordered Filter chain for one direction on a model connection. Only text-kind Filters may be assigned.
request runs before dispatch to the upstream provider — a match can redact the prompt or block the call. response runs on the streamed completion; multi-chunk patterns are inspected inside the LLM outbound filter window.
Tool guards filters list
dome tool guards filters list <connection>
List the JSON Filters assigned to an MCP server (tool) connection, in chain order, grouped by direction.
Tool guards filters set
dome tool guards filters set <connection>
Replace the entire ordered Filter chain for one direction on a tool connection. Only json-kind Filters may be assigned.
request filters run over tool arguments before the call reaches the upstream MCP server — matched fields are redacted or omitted, or the whole call is blocked. response filters run over the tool result before the agent sees it.