app_launch · K-Personal MCP: Risk & Policy

WHAT IT DOES

What app_launch does on K-Personal MCP

AI agents invoke app_launch to trigger actions in K-Personal MCP. 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 app_launch needs a policy

This tool executes external applications and programs on the desktop without reversible constraints. An AI agent could launch malicious, resource-intensive, or destructive applications (e.g., system tools, wipers, fork bombs, or apps that perform unauthorized actions). While not inherently destructive itself, execution depends entirely on which app is launched, making it a high-severity Execute-class tool.

From the tool's definition Tool name 'app_launch' combined with description stating it executes applications via registered aliases or executable file paths (Korean: '앱을 실행합니다. 등록된 별명 또는 실행파일 경로를 넣습니다'). This directly launches arbitrary applications on the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

app_launch Rate-limited

app_launch 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": {
    "app_launch": {
      "limits": [
        {
          "counter": "app_launch_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 K-Personal MCP, so you can run agents against it safely.

FAQ

Questions about app_launch

What does the app_launch tool do? +

앱을 실행합니다. 등록된 별명 또는 실행파일 경로를 넣습니다. It is categorised as a Execute tool in the K-Personal MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on app_launch? +

Register the K-Personal MCP server in PolicyLayer and add a rule for app_launch: 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 K-Personal MCP. Nothing to install.

What risk level is app_launch? +

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

Can I rate-limit app_launch? +

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

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

app_launch is provided by the K-Personal MCP server (lee30934-byte/k-personal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.