system_execute_command · PC-Control MCP Server MCP

WHAT IT DOES

What system_execute_command does on PC-Control MCP Server

AI agents invoke system_execute_command to trigger actions in PC-Control 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 system_execute_command needs a policy

This tool allows execution of arbitrary shell commands on the host machine, which is a classic Execute category action. The blast radius is critical because shell commands can read/write/delete files, install malware, exfiltrate data, modify system configuration, launch attacks on networks, or cause denial of service.

From the tool's definition Tool name 'system_execute_command' combined with description 'Execute a shell command on the host machine' directly indicates arbitrary code execution capability on the underlying Windows system.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

system_execute_command Rate-limited

system_execute_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": {
    "system_execute_command": {
      "limits": [
        {
          "counter": "system_execute_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 PC-Control MCP Server, so you can run agents against it safely.

FAQ

Questions about system_execute_command

What does the system_execute_command tool do? +

Execute a shell command on the host machine. It is categorised as a Execute tool in the PC-Control 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 system_execute_command? +

Register the PC-Control MCP Server MCP server in PolicyLayer and add a rule for system_execute_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 PC-Control MCP Server. Nothing to install.

What risk level is system_execute_command? +

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

Can I rate-limit system_execute_command? +

Yes. Add a rate_limit block to the system_execute_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 system_execute_command completely? +

Set action: deny in the PolicyLayer policy for system_execute_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 system_execute_command? +

system_execute_command is provided by the PC-Control MCP Server MCP server (krsnmlna1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.