High Risk →

terminate_app

Terminate a running app on a simulator

How to control terminate_app ↓

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

High Risk

This tool stops/kills a running application process on a simulator. It executes an action (process termination) that affects the running state of an app. While not permanently destructive (the app can be relaunched), it does interrupt execution and could disrupt workflows. It fits Execute as it triggers an external operation (terminating a process) whose effect depends on which app is targeted.

From the tool's definition Terminate a running app on a simulator

Documented attack patterns abuse exactly the kind of access terminate_app gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Xcode, and nothing reaches the server without passing your rules. This is the rule we recommend for terminate_app:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "terminate_app": {
      "limits": [
        {
          "counter": "terminate_app_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

terminate_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.

  1. Create a free account and register Xcode — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the terminate_app tool do? +

Terminate a running app on a simulator. It is categorised as a Execute tool in the Xcode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on terminate_app? +

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

What risk level is terminate_app? +

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

Can I rate-limit terminate_app? +

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

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

terminate_app is provided by the Xcode MCP server (xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xcode tool call.

Deterministic rules across all 69 Xcode tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

69 Xcode tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.