mcp-dlp
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 |
|---|---|
| read_documentA | Read a document from the mock Google Drive by filename, with DLP scanning, redaction, and a fail-closed block policy for credentials/secrets. |
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.
The single tool name follows a verb_noun pattern (read_document), which is clear and consistent. No other tools exist to create inconsistency.
One tool is too few for a DLP server; typical DLP functionality would require multiple tools for managing documents, rules, and scanning. The count feels insufficient.
The server only provides a single read operation with DLP scanning. Missing essential tools for document management, rule configuration, and other DLP operations, making it severely incomplete.