sync_destroy

Destroy a sync group and release resources.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/sync-destroy.md

WHAT IT DOES

What sync_destroy does on Claude Mobile

AI agents call sync_destroy to permanently remove resources in Claude Mobile, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why sync_destroy is rated Critical

This tool performs an irreversible operation that cannot be undone. Destroying a sync group likely removes synchronization settings, group associations, or shared state that cannot be recovered without manual reconfiguration. While not as critical as data deletion across files, the permanent removal of a configured system component (sync group) with resource deallocation qualifies as Destructive.

From the tool's definition Tool name is 'sync_destroy' with description 'Destroy a sync group and release resources.' The verb 'destroy' combined with 'release resources' indicates irreversible deletion or deallocation of a sync group configuration or data structure.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sync_destroy Hidden

sync_destroy is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sync_destroy"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sync_destroy

What does the sync_destroy tool do? +

Destroy a sync group and release resources. It is categorised as a Destructive tool in the Claude Mobile MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sync_destroy? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for sync_destroy: 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.

What risk level is sync_destroy? +

sync_destroy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sync_destroy? +

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

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

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

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →