sync
Multi-device sync testing. create_group: bind devices to roles. run: coordinated steps with barriers. assert_cross: act on A, verify on B. status: group details. list: all groups. destroy: cleanup.
This record as markdown: /tools/alexgladkov-claude-in-mobile/sync.md
What sync does on Claude Mobile
AI agents invoke sync 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 is rated High
The tool's primary purpose is to execute coordinated actions across multiple devices simultaneously (run coordinated steps, assert cross-device interactions). While it includes a 'destroy' sub-action for cleanup, the dominant use case is triggering and orchestrating multi-device operations.
From the tool's definition 'coordinated steps with barriers', 'act on A, verify on B', 'run: coordinated steps' — orchestrates active operations across multiple devices; 'destroy: cleanup' implies teardown but primary function is multi-device execution coordination
Attacks that exploit this kind of access
The rule that runs sync 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, this is the rule to start with:
sync 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every sync call is checked against it from then on.
Questions about sync
Multi-device sync testing. create_group: bind devices to roles. run: coordinated steps with barriers. assert_cross: act on A, verify on B. status: group details. list: all groups. destroy: cleanup. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for sync: 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 Claude Mobile. Nothing to install.
sync is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sync 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.
Set action: deny in the PolicyLayer policy for sync. 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.
sync is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue