safe-agent-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 |
|---|---|
| run_commandA | 在沙箱中执行一条 shell 命令，返回 stdout、stderr 和退出码。注意：command 只填命令本身（如 echo hello），不要传 JSON 包装。 |
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 name 'run_command' clearly describes its function, eliminating any ambiguity.
The single tool follows a consistent verb_noun pattern ('run_command'). There are no other tools to create inconsistency, so the naming is perfectly consistent.
The server has only one tool, which feels thin for a typical tool set. While it may cover the core purpose of safe command execution, the surface is minimal and could benefit from additional related tools.
The server's stated purpose is to execute shell commands in a sandbox, and 'run_command' fully covers this operation by returning stdout, stderr, and exit code. No obvious gaps exist for the intended scope.