mcp-policy-guardian
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_repo_policyA | Deterministic check for standard repository governance artifacts. Network-free, read-only, fail-closed. Stable keys: tool, repo_path, ok, checks, fail_closed |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
The single tool name 'check_repo_policy' follows a clear verb_noun pattern, consistent with itself.
One tool is minimal but may be acceptable for a very narrow single-purpose server. However, given the server name 'Policy Guardian', a broader set of policy management tools would be expected.
The tool only checks for standard repository governance artifacts. There are no tools for applying policies, reporting, or managing exceptions, leaving significant gaps for a policy guardian server.