Finding a Hidden SafeMode Gap in Under a Minute with Fusion MCP and Claude
Slides are a poor way to show what a platform can do. A live problem, solved while the customer watches, shows it much better.
An Everpure SE recently ran a Fusion enablement call with a customer who had been trying to track down a SafeMode misconfiguration on one of their arrays. They had looked but couldn’t find it.
Partway through the session, the SE connected Claude to the customer’s environment through the Pure Fusion MCP server. Instead of clicking through array settings one at a time, the SE asked questions about the fleet in plain language and had Claude review the SafeMode configuration across it.
Within a minute, the team had the answer: Per-object SafeMode wasn’t enabled on that array.
What is Per-object SafeMode?
SafeMode is Pure’s immutable snapshot protection, built to keep ransomware or a compromised admin account from destroying your recovery points. An intruder can’t set snapshot retention to zero and eradicate everything, and retention can only be shortened through Pure Support, with identity confirmed first.
SafeMode started as an array-wide setting: all or nothing. Per-object SafeMode (also called Object-level SafeMode, or Per Protection Group SafeMode in earlier material) lets you enable it on specific protection groups instead, so you can focus protection on your most critical volumes.
It works through the protection group’s retention lock:
Unlocked: anyone with access can lower the snapshot schedule, shorten retention, or disable it.
Ratcheted: retention can only go up. Lowering or degrading it requires Pure Support.
SafeMode also comes in two newer forms:
Default Protection SafeMode sets a default protection group for an array container, so any new volume inherits its snapshot and retention policies.
Auto-On SafeMode turns protection on by default for new arrays, with no setup required.
Why a gap here is easy to miss
Because protection can be set per protection group, it can differ from group to group and from array to array. A snapshot schedule can look healthy while the retention lock behind it is still unlocked. That’s hard to spot when you’re checking arrays one at a time, and it matters most when someone with stolen credentials is trying to delete your snapshots.
Why it matters
A real data-protection gap, closed. SafeMode is a core part of a ransomware resilience strategy, and a misconfiguration there is exactly what you want to catch before an incident. Finding it strengthened the customer’s security posture right away.
Fleet-wide visibility, shown rather than told. Fusion gives you one control plane across your arrays. Adding an AI assistant on top means you can ask a question about the whole fleet and get a fast, direct answer instead of auditing array by array.
A better conversation. The call started as a standard feature walkthrough. Once the gap turned up, it became a real problem solved on the spot, and the customer responded very positively to the integration.
The takeaway
Configuration drift is easy to miss, especially across many arrays with per-group protection settings. Pairing Fusion’s single control plane with Claude through MCP turned a problem the team couldn’t find into a one-minute answer.
If you’re curious how this could work in your environment, reach out to your Everpure team and we can walk through it live.