Open or focus a macOS application by name. Prefer batch_actions when combining with other actions.
AI agents invoke launch_app to trigger actions in Macos Control. 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.
While launching an app might seem benign, it executes an external operation whose downstream effects depend entirely on the application launched and what an AI agent causes that app to do next. Combined with sibling tools like execute_javascript, click_at, and fill_by_label, this becomes part of a capability chain for autonomous macOS control.
From the tool's definition launch_app can 'Open or focus a macOS application by name' and the server description states it gives 'AI agents eyes and hands on macOS.' Launching applications is executing external operations that trigger system behavior beyond the tool's direct control.
Documented attack patterns abuse exactly the kind of access launch_app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Macos Control, and nothing reaches the server without passing your rules. This is the rule we recommend for launch_app:
{
"version": "1",
"default": "deny",
"tools": {
"launch_app": {
"limits": [
{
"counter": "launch_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Open or focus a macOS application by name. Prefer batch_actions when combining with other actions. It is categorised as a Execute tool in the Macos Control MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Macos Control 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 Macos Control. 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 Macos Control MCP server (peterhdd/macos-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Macos Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Macos Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.