bazel_daemon_stop

What bazel_daemon_stop does on XcodeBazelMCP

AI agents invoke bazel_daemon_stop 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.

Why bazel_daemon_stop is rated High

This tool executes a command to stop a background daemon process and clear associated metadata. While not destructive to user data (the daemon can be restarted), it triggers an external operation whose effects are immediate and irreversible until the daemon is restarted. This fits the Execute category: it runs a command that triggers external operations whose effects depend on context.

From the tool's definition Tool description states 'Stop the per-workspace background daemon and clear its tracked operation metadata.' The action of stopping a daemon and clearing its state represents executing a control operation that halts running processes and modifies system state.

The rule that runs bazel_daemon_stop 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_daemon_stop, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bazel_daemon_stop": {
      "limits": [
        {
          "counter": "bazel_daemon_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about bazel_daemon_stop