Damn Vulnerable MCP Server (DVMCP)

Overview Schema Source Related Servers Discussions Admin

it.execute_admin_command

Execute shell commands with optional sudo elevation for system maintenance and troubleshooting.

Instructions

Run administrative system commands for maintenance and troubleshooting. Supports shell commands with optional sudo elevation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "it.execute_admin_command"
  }
}

Input Schema

Name	Required	Description
`command`	Yes	Shell command to execute
`sudo`	No	Run with elevated privileges
`timeout`	No	Timeout in seconds (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jun 22, 2026

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It mentions 'optional sudo elevation,' which hints at privileged execution, but it does not disclose potential destructive side effects, required permissions, or output behavior. For a tool that runs arbitrary shell commands, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the purpose. Every word contributes: the first sentence states the action and context, the second mentions shell commands and sudo. No redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-risk admin command execution tool, the description is underpowered. It lacks any mention of return values, error handling, timeout behavior despite the schema having a timeout parameter, or warnings about irreversible changes. The schema partially covers parameters but the overall tool behavior is not fully described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter detail beyond what the schema already provides; it only restates that shell commands and sudo are supported. No extra syntax, format, or edge-case info is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states what the tool does: 'Run administrative system commands for maintenance and troubleshooting.' The verb 'Run' and resource 'administrative system commands' make the primary action explicit. It distinguishes from siblings like it.query_audit_log or it.get_system_config by focusing on command execution, though it does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for maintenance and troubleshooting' provides clear context for when to use the tool. However, it does not mention when not to use it or explicitly compare with alternatives, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.