system_run_command

What system_run_command does on AutoCAD MCP Pro

AI agents invoke system_run_command to trigger actions in AutoCAD MCP Pro. 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 system_run_command is rated High

A tool named 'system_run_command' that executes system commands represents Execute-level risk (or potentially Destructive/critical depending on what commands can be run). On a production CAD automation server integrated with AI agents, this poses extreme blast radius: attackers or misdirected agents could execute arbitrary code, modify files, exfiltrate data, or compromise the system.

From the tool's definition Tool name 'system_run_command' indicates execution of arbitrary system commands; description is empty but the name alone is a strong signal for command execution capability in an AutoCAD automation context.

Risk signalsAdmin/system-level operation

The rule that runs system_run_command safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AutoCAD MCP Pro, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_run_command, this is the rule to start with:

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

Questions about system_run_command