execute_system_command · Vulnerable MCP Server MCP

WHAT IT DOES

What execute_system_command does on Vulnerable MCP Server

AI agents invoke execute_system_command to trigger actions in Vulnerable MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_system_command needs a policy

System command execution is a classic Execute category risk—it runs code whose effects depend entirely on user input. In a pentest lab context with deliberately insecure design, this poses critical severity: an AI agent could delete files, exfiltrate data, pivot to other systems, or cause widespread damage via shell commands. High confidence despite empty description because the name alone is unambiguous.

From the tool's definition Tool name is 'execute_system_command' with no description provided. The name explicitly indicates execution of arbitrary system commands, which can trigger external operations with effects dependent on arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_system_command Rate-limited

execute_system_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_system_command": {
      "limits": [
        {
          "counter": "execute_system_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vulnerable MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_system_command

What does the execute_system_command tool do? +

execute_system_command. It is categorised as a Execute tool in the Vulnerable MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_system_command? +

Register the Vulnerable MCP Server MCP server in PolicyLayer and add a rule for execute_system_command: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Vulnerable MCP Server. Nothing to install.

What risk level is execute_system_command? +

execute_system_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_system_command? +

Yes. Add a rate_limit block to the execute_system_command rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block execute_system_command completely? +

Set action: deny in the PolicyLayer policy for execute_system_command. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides execute_system_command? +

execute_system_command is provided by the Vulnerable MCP Server MCP server (joyghoshs/vulnerable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.