launch_mac_app · Sl Test MCP: Risk & Policy

WHAT IT DOES

What launch_mac_app does on Sl Test

AI agents invoke launch_mac_app to trigger actions in Sl Test. 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 launch_mac_app needs a policy

This tool executes arbitrary macOS applications based on user-supplied appPath arguments. An AI agent with misuse could launch malicious applications, system tools for privilege escalation, or applications that exfiltrate data. While not inherently destructive or financial, it triggers external operations whose effects depend entirely on which application is launched, making it Execute category.

From the tool's definition The tool "Launches a macOS application" by executing an application specified by appPath parameter. This is a direct external operation trigger that runs code/binaries on the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

launch_mac_app Rate-limited

launch_mac_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_mac_app": {
      "limits": [
        {
          "counter": "launch_mac_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 Sl Test, so you can run agents against it safely.

FAQ

Questions about launch_mac_app

What does the launch_mac_app tool do? +

Launches a macOS application. IMPORTANT: You MUST provide the appPath parameter. Example: launch_mac_app({ appPath:. It is categorised as a Execute tool in the Sl Test 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_mac_app? +

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

What risk level is launch_mac_app? +

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

Can I rate-limit launch_mac_app? +

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

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

launch_mac_app is provided by the Sl Test MCP server (sampsonky/xcodebuildmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.