launch_app

Launch an application by name. Lightweight — just activates the app without reading its accessibility tree.

SERVERAirMCP SOURCEairmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/launch-app.md

WHAT IT DOES

What launch_app does on AirMCP

AI agents invoke launch_app to trigger actions in AirMCP. 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.

RISK

Why launch_app is rated High

Launch_app executes arbitrary application code on the user's system. While lightweight (no data access), the impact depends entirely on the argument—an AI agent given this tool could launch keyloggers, malware, or systemically dangerous applications. This is Execute rather than Write because it triggers external processes whose effects are not reversible and not limited to data mutation.

From the tool's definition Tool launches an application by name — a direct action that triggers execution of external processes with side effects determined by which app is specified. Description confirms it 'activates the app', a runtime operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs launch_app safely

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

launch_app Rate-limited

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": {
    "launch_app": {
      "limits": [
        {
          "counter": "launch_app_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every launch_app call is checked against it from then on.

FAQ

Questions about launch_app

What does the launch_app tool do? +

Launch an application by name. Lightweight — just activates the app without reading its accessibility tree. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on launch_app? +

Register the Air MCP server in PolicyLayer and add a rule for 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 AirMCP. Nothing to install.

What risk level is launch_app? +

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

Can I rate-limit launch_app? +

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

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

launch_app is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools → High-risk tools on this server →

Across the catalogue

disable_passenger_app on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →