agent-guardrail
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GUARDRAIL_POLICY | No | Path to the policy YAML file to use. If not set, falls back to the bundled default policy. |
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 |
|---|---|
| guardrail_checkA | Evaluate a proposed tool call against the Guardrail policy BEFORE executing it. Returns ALLOW, WARN, or BLOCK with a concrete explanation. Always call this before performing any action that spends money, deletes data, sends messages externally, or runs code. |
| guardrail_record_outcomeA | Record the real-world outcome (success/error) of a previously-checked action, for the audit trail. |
| guardrail_agent_historyB | Return recent decision history for a given agent — a real, persisted audit trail. |
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 covers a distinct phase of the guardrail lifecycle: pre-action evaluation, post-action outcome recording, and historical audit retrieval. There is no functional overlap between check, record_outcome, and agent_history, making tool selection unambiguous.
All tools share a consistent 'guardrail_' prefix, with two using a verb_noun pattern (guardrail_check, guardrail_record_outcome). The third, guardrail_agent_history, uses a noun phrase instead of a verb, which is a minor deviation but still predictable and readable.
Three tools is well-scoped for a guardrail server, providing the core operations of checking, recording, and viewing history without unnecessary bloat. This is within the ideal range and earns its place.
The tool set covers the entire guardrail workflow: evaluate before action, record the outcome afterward, and retrieve an audit trail. There are no obvious dead ends or missing critical operations for this focused domain.