MCP Shield
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 |
|---|---|
| scan_path_toolC | Scan a local MCP server or agent project for security risks. |
| list_rulesA | List MCP Shield rule IDs and descriptions. |
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 2 tools
The two tools have clearly distinct purposes: one lists all rule IDs and descriptions, the other scans a specific path. No overlap in functionality.
Both tools use snake_case and a verb_noun pattern. 'scan_path_tool' has an extra '_tool' suffix, but this is a minor deviation from the pattern of list_rules.
Only 2 tools for a security-focused MCP server is very limited. A typical security tool would require additional actions like rule details, scan results, or configuration.
The server lacks essential operations: ability to get details of individual rules, view scan results, configure scans, or take actions based on findings. Significant gaps for a security scanning server.