ai-security-gateway-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_promptA | Scans text for PII (personally identifiable information) before sending to an LLM. Detects emails, phone numbers, credit cards, Aadhaar numbers, PAN cards, IP addresses, passports, and bank accounts. Returns risk level, findings, and anonymized text. Always run this before sending sensitive prompts to any LLM. |
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
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly defined and distinct.
The tool name 'scan_prompt' follows a clear verb_noun convention, which is consistent even though there is only one tool. No conflicting naming styles are present.
The server is named 'ai-security-gateway', implying a broader set of security functions, but it exposes only a single tool. This feels far too thin for the apparent scope, which likely requires multiple operations like output scanning or configuration.
The server only scans input prompts for PII and anonymizes them. It lacks other critical gateway features such as output scanning, response filtering, or policy management, making the surface severely incomplete for a security gateway.