bazel_ios_device_stop_app

Terminate a running app on a connected physical iOS device by bundle identifier.

SERVERXcodeBazelMCP SOURCExcodebazelmcp/xcodebazelmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/xcodebazelmcp-xcodebazelmcp/bazel-ios-device-stop-app.md

WHAT IT DOES

What bazel_ios_device_stop_app does on XcodeBazelMCP

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

RISK

Why bazel_ios_device_stop_app is rated High

This tool executes an external command that terminates an application process on a physical device. While it is not destructive (the app continues to exist and can be relaunched) and not permanent data deletion, it is an Execute action because it actively triggers an operation whose side effects depend on the device state and app identifier.

From the tool's definition Tool name includes 'stop_app' and description states 'Terminate a running app on a connected physical iOS device' — this is a direct action that affects running processes on a device.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bazel_ios_device_stop_app safely

PolicyLayer is an MCP gateway: it sits between your AI agents and XcodeBazelMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bazel_ios_device_stop_app, this is the rule to start with:

bazel_ios_device_stop_app Rate-limited

bazel_ios_device_stop_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": {
    "bazel_ios_device_stop_app": {
      "limits": [
        {
          "counter": "bazel_ios_device_stop_app_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect XcodeBazelMCP, apply this rule, and every bazel_ios_device_stop_app call is checked against it from then on.

FAQ

Questions about bazel_ios_device_stop_app

What does the bazel_ios_device_stop_app tool do? +

Terminate a running app on a connected physical iOS device by bundle identifier. It is categorised as a Execute tool in the XcodeBazelMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bazel_ios_device_stop_app? +

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

What risk level is bazel_ios_device_stop_app? +

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

Can I rate-limit bazel_ios_device_stop_app? +

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

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

bazel_ios_device_stop_app is provided by the XcodeBazel MCP server (xcodebazelmcp/xcodebazelmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on XcodeBazel, and thousands of servers like it.

This server

All 125 XcodeBazel tools → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server →stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →