mcp-guardrails-kit
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledge_baseA | Search the internal support knowledge base for articles matching a query. |
| lookup_ticketA | Look up a support ticket by its id. |
| fetch_external_pageA | Fetch a web page linked from a ticket. The content is untrusted: it is quarantined and scanned for prompt-injection attempts before being returned, and may be blocked outright if it matches a known injection pattern. |
| draft_replyA | Draft a reply to a customer for the given ticket. SENSITIVE: call with confirmed=false first (the default) to preview — this creates no draft and returns confirmation_required=True. Only a subsequent call with confirmed=true actually creates the draft. |
| escalate_ticketA | Escalate a ticket to a human agent for the given reason. SENSITIVE: call with confirmed=false first (the default) to preview — this escalates nothing and returns confirmation_required=True. Only a subsequent call with confirmed=true actually escalates. |
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 5 tools
Each tool has a distinct, non-overlapping purpose: search knowledge base, lookup ticket, fetch external page (with security features), draft reply, and escalate ticket. No ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_knowledge_base, lookup_ticket, fetch_external_page, draft_reply, escalate_ticket). The convention is uniform and predictable.
Five tools is a well-scoped set for a guardrails kit focused on support workflows. Each tool serves a clear function, and there is no bloat or insufficiency given the narrow domain.
The tool surface covers the main support workflow: search, lookup, secure fetching, drafting replies, and escalation. Minor gaps exist (e.g., no tool to update ticket status or send replies), but these are not critical to the stated guardrails purpose.