remediation-flight-recorder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| remediation_preflightB | Create a policy-gated remediation transaction and compute blast radius and rollback plan. |
| remediation_approveA | Record explicit human/operator approval for a preflighted transaction. |
| remediation_record_executionB | Bind execution receipts to an approved transaction; this package does not execute remote commands itself. |
| remediation_verifyC | Compare a post-remediation exposure snapshot with declared expectations. |
| remediation_record_rollbackB | Bind rollback receipts to a transaction that entered rollback state. |
| remediation_verify_ledgerB | Verify both payload hashes and the local tamper-evident evidence chain. |
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 6 tools
Each tool targets a distinct lifecycle stage: preflight, approve, record execution, verify, record rollback, and verify ledger. There is no overlap in purpose or state transition.
All tools follow a consistent remediation_<verb> pattern, with verbs clearly indicating the action (preflight, approve, record_execution, verify, record_rollback, verify_ledger).
Six tools cover the full remediation workflow without redundancy. The count is well-scoped for a focused domain.
The lifecycle is well covered: create, approve, execute, verify, rollback, and ledger verification. A minor gap is the lack of a tool to query transaction status or history, but the core workflow is complete.