launch_app
Launch an application by name. Lightweight — just activates the app without reading its accessibility tree.
This record as markdown: /tools/io-github-heznpc-iconnect/launch-app.md
What launch_app does on Iconnect
AI agents invoke launch_app to trigger actions in Iconnect. 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 launch_app is rated High
This tool runs/launches an external application, which is an Execute-category action. It has high severity because an AI agent could be tricked into launching malicious, system-critical, or resource-intensive applications. However, it stops short of Destructive (no data loss) or Financial (no money movement), and the lightweight nature means it doesn't read system state deeply.
From the tool's definition Tool description states it 'Launch[es] an application by name' and 'activates the app'. Launching applications is an Execute action that triggers external operations whose effects depend on arguments (which app is launched).
Attacks that exploit this kind of access
The rule that runs launch_app safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every launch_app call is checked against it from then on.
Questions about launch_app
Launch an application by name. Lightweight — just activates the app without reading its accessibility tree. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect 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 Iconnect. Nothing to install.
launch_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
launch_app is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue