agentguard-mcp
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 |
|---|---|
| check_urlA | Check whether a URL is allowed under a network policy. Returns { allowed, reason } without making any actual request. Use this to gate tool calls before they execute. |
| check_urls_batchA | Batch-check multiple URLs against the same policy. Returns per-URL decisions plus an allowed/denied summary. Useful for vetting a list of pending tool fetches. |
| validate_policyA | Sanity-check a policy spec without making any decision. Catches: empty allow list, overly broad "*" wildcards, malformed host patterns containing schemes/paths/queries. |
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 has a clearly distinct purpose: single URL check, batch URL check, and policy validation. No overlap or ambiguity.
All tools use snake_case and a clear verb_noun pattern. 'check_urls_batch' slightly deviates by appending 'batch' as a suffix, but is still understandable and consistent in style.
With 3 tools, the server is well-scoped for its purpose of URL checking and policy validation. Each tool serves a necessary function without excess.
The tool set covers the core use cases: checking individual or multiple URLs, and validating policy specs. It lacks policy management tools (create/update/delete), but that may be out of scope for a 'checker' server.