agent-sudo-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileC | Read a local file through agent-sudo policy enforcement. |
| write_fileA | DEMO/REFERENCE executor: classifies and gates the write through agent-sudo, then writes inside the configured workspace (defaults to /tmp/agent-sudo-demo if no workspace is configured). It does not write to arbitrary paths outside the workspace. |
| run_shell_commandA | DEMO/REFERENCE executor: classifies and gates the command through agent-sudo, then executes only a narrow allowlist. It is not a general shell. To gate real commands, embed the agent-sudo authorization engine in your agent (see README). |
| get_runtime_contextA | Get current working directory, git repository root, active branch, and workspace status details. |
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 4 tools
Each tool has a distinct purpose: getting runtime context, reading files, running shell commands, and writing files. No overlap in functionality.
All tool names follow the verb_noun pattern (get_runtime_context, read_file, run_shell_command, write_file), providing a consistent and predictable interface.
With 4 tools, the server is well-scoped for its demo/reference purpose. The count is not too low or too high for the functionality offered.
The tools cover the core operations (read, write, execute, context), but it lacks common file operations like listing or deletion, which may be needed for full workflows.