permission-aware-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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | Read a UTF-8 text file from the data directory. (Risk: LOW) |
| write_fileA | Write content to a file in the data directory. (Risk: MEDIUM) Modifies data; requires human approval unless policy allows it. |
| delete_fileA | Delete a file from the data directory. (Risk: HIGH) Destructive; requires explicit human approval. |
| execute_commandA | Execute a system command (SIMULATED). (Risk: CRITICAL) Denied by default. Never runs a real subprocess. |
| approve_operationA | Approve and execute a pending This is the ONLY way an |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| security_review | Generate a security-review prompt for an operation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_audit_log | The structured audit log (human-readable rendering). |
| get_permissions_config | The current permission policy as JSON. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: read, write, delete files; execute commands; and approve operations. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern, e.g., read_file, delete_file, approve_operation. This makes the tool surface predictable and easy to navigate.
With 5 tools, the server is well-scoped for its purpose of providing permission-aware file and command operations. Each tool earns its place without unnecessary complexity.
Core file operations (read, write, delete) and command execution are covered. Minor gaps include the lack of a list/directory tool and no way to view pending approvals, but the essential workflow is complete.