MCP Security Framework
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_DIR | No | Directory for log files. If not set, defaults to ./logs. Use when the process may run with a non-writable working directory. | |
| TOOL_POLICIES_PATH | No | Path to a JSON file containing tool policies configuration. If not set, looks for tool-policies.json in the current working directory or ~/.config/mcp-secure-server/tool-policies.json. |
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 |
|---|---|
| debug-calculatorB | Simple calculator for testing |
| debug-file-readerC | File reader for testing |
| debug-echoB | Echo tool for testing |
| debug-databaseC | Mock database operations using safe predefined queries |
| debug-httpB | Mock HTTP request with URL validation (whitelist pattern) |
| debug-parserC | JSON/XML parser with size limits |
| debug-imageC | Mock image processing with directory restrictions |
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 7 tools
Each tool has a distinct domain (calculator, database, echo, file reading, HTTP, image processing, parsing) with no functional overlap, making them easy to distinguish.
All tools follow a consistent 'debug-<noun>' pattern with hyphens, providing a clear and predictable naming convention.
Seven tools is well-scoped for a debugging/testing framework, covering essential operations without excess.
The tools cover a broad range of typical debugging scenarios (arithmetic, database, file I/O, HTTP, image processing, parsing) with safety restrictions, leaving no obvious gaps.