simulator_terminate_app · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What simulator_terminate_app does on Xclaude Plugin

AI agents invoke simulator_terminate_app to trigger actions in Xclaude Plugin. 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 simulator_terminate_app needs a policy

This tool sends a termination signal to a running application on an iOS simulator. It triggers an external operation (process termination) that affects the simulator's runtime state. While the effect is reversible (the app can be relaunched), it actively executes an action against a running process, placing it in the Execute category. Misuse could interrupt ongoing operations or testing workflows.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulator_terminate_app Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "simulator_terminate_app": {
      "limits": [
        {
          "counter": "simulator_terminate_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 Xclaude Plugin, so you can run agents against it safely.

FAQ

Questions about simulator_terminate_app

What does the simulator_terminate_app tool do? +

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

How do I enforce a policy on simulator_terminate_app? +

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

What risk level is simulator_terminate_app? +

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

Can I rate-limit simulator_terminate_app? +

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

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

simulator_terminate_app is provided by the Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

simulator_terminate_app is one line of Xclaude Plugin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →