system_launch_app · PC-Control MCP Server MCP: Risk & Policy

WHAT IT DOES

What system_launch_app does on PC-Control MCP Server

AI agents invoke system_launch_app 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_launch_app needs a policy

Launching applications executes code and triggers external operations whose effects depend on arguments (the app name/path). An AI agent could launch malware, resource-intensive processes, or applications that exfiltrate data or harm the system. This is Execute, not Write, because the action cannot be easily reversed and its side effects are determined by what application runs.

From the tool's definition Launches an application by name or path; part of a server that 'Enables control of Windows PC through Claude Desktop, including executing shell commands, managing system resources, controlling audio/power, launching applications' — launching applications is…

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

system_launch_app Rate-limited

system_launch_app 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_launch_app": {
      "limits": [
        {
          "counter": "system_launch_app_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_launch_app

What does the system_launch_app tool do? +

Launch an application by name or path. 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_launch_app? +

Register the PC-Control MCP Server MCP server in PolicyLayer and add a rule for system_launch_app: 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_launch_app? +

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

Can I rate-limit system_launch_app? +

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

Set action: deny in the PolicyLayer policy for system_launch_app. 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_launch_app? +

system_launch_app 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.