sync_run

What sync_run does on Claude Mobile

AI agents invoke sync_run to trigger actions in Claude Mobile. 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 sync_run is rated High

This tool executes arbitrary coordinated steps across Android/iOS devices via ADB and simctl. While it does not permanently delete data or move money, it can trigger external operations (app interactions, UI automation, system commands) whose effects depend on the specific steps provided. The multi-device synchronization amplifies the blast radius—a misconfigured sequence could affect multiple devices simultaneously.

From the tool's definition Tool name 'sync_run' combined with description 'Execute coordinated steps across devices with barrier synchronization' explicitly uses the verb 'Execute' and indicates it runs coordinated operations across multiple mobile devices.

The rule that runs sync_run safely

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

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

Questions about sync_run