quit_app · Mac MCP: Risk & Policy

WHAT IT DOES

What quit_app does on Mac

AI agents invoke quit_app to trigger actions in Mac. 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 quit_app needs a policy

Quitting an application is an external operation that affects running processes. While it's a 'graceful' quit (not force-kill), it terminates an application which can cause loss of unsaved work and disrupt workflows. It's not purely destructive (doesn't delete data) but executes an external system operation with real side effects depending on which app is targeted.

From the tool's definition Gracefully quits an application by name

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quit_app Rate-limited

quit_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": {
    "quit_app": {
      "limits": [
        {
          "counter": "quit_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 Mac, so you can run agents against it safely.

FAQ

Questions about quit_app

What does the quit_app tool do? +

Gracefully quits an application by name. It is categorised as a Execute tool in the Mac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on quit_app? +

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

What risk level is quit_app? +

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

Can I rate-limit quit_app? +

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

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

quit_app is provided by the Mac MCP server (laststance/mac-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.