Clotr Guard
OfficialServer 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.
Clotr checks text on this computer and returns each finding's kind and a masked form, never the full value. Call check_text before you send text that may hold a credential to another tool or service. Call clean_text when you want a copy with the findings replaced. Call is_secret_file before you read a local file. Clotr checks only what you pass it and stops nothing itself.
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 |
|---|---|
| check_textA | Check text for credentials before it leaves this computer or goes to another tool. Returns kinds and masked forms, and blocks nothing. |
| clean_textA | Runs check_text's check and returns the text with each finding replaced by a placeholder, plus their kinds and masked forms. |
| is_secret_fileA | Call before reading a local file. True means Clotr treats the path as a secret file, so don't read it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 3 tools
check_text and clean_text operate on the same input (text) and could be confused at a glance, but the descriptions clearly differentiate detection-only from redaction-with-placeholders. is_secret_file targets a completely different resource (file paths) and is unambiguous.
check_text and clean_text follow a consistent verb_noun pattern, and is_secret_file is a readable predicate form that fits its boolean-returning behavior. The minor deviation in style (is_ prefix) is natural and doesn't impede understanding.
Three tools is a tight, well-scoped surface for a credential-guard utility: detect, redact, and path-check. Each tool clearly earns its place with no filler.
The core lifecycle — check text, clean text, and vet file paths before reading — is covered. Minor gaps exist, such as no tool for scanning file contents directly or configuring custom detection patterns, but agents can compose the existing tools to work around this.