---
title: "Comment by OnlineProxy on \"iOS Cloud Phone Fleets: Driving 50 Snapchat Sessions with an MCP Agent\" | Hashnode"
description: "the snapchat enforcement claims are anecdotal. it also contradicts itself, since you want one device and proxy per account for life but wipe and reuse a pool of"
url: "https://hashnode.com/posts/ios-cloud-phone-fleet-snapchat-mcp-agent/6ab6f3efa9d725b4d84c0c7d/comment/6abc419dcd1cf39f8fe1d08f"
---

[Discussion](https://hashnode.com/posts/ios-cloud-phone-fleet-snapchat-mcp-agent/6ab6f3efa9d725b4d84c0c7d)

Comment [iOS Cloud Phone Fleets: Driving 50 Snapchat Sessions with an MCP Agent](https://hashnode.com/posts/ios-cloud-phone-fleet-snapchat-mcp-agent/6ab6f3efa9d725b4d84c0c7d)

[OnlineProxy](https://hashnode.com/@onlineproxyio)

[Sep 29](https://hashnode.com/posts/ios-cloud-phone-fleet-snapchat-mcp-agent/6ab6f3efa9d725b4d84c0c7d/comment/6abc419dcd1cf39f8fe1d08f)

the snapchat enforcement claims are anecdotal. it also contradicts itself, since you want one device and proxy per account for life but wipe and reuse a pool of 8 to 10 devices across 50 accounts

apple's risk metric counts attested keys per app per device over 30 days and grows with reinstalls, so my guess is reused devices show a rising count, but that's just my reasoning and i don't know if snapchat uses it. i'd also add human approval and a kill switch to run\_task, since it reads inbox content nobody controls and can then post and message, which is a prompt injection path
