hetzner_rollback_storage_box_snapshot

Roll a Storage Box back to a previous snapshot. ⚠️ DESTRUCTIVE: this overwrites the current state of the Storage Box. Any data written after the snapshot was taken will be lost. The \

Server Hetzner MCP Server jurislm/hetzner-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What hetzner_rollback_storage_box_snapshot does on Hetzner MCP Server

AI agents call hetzner_rollback_storage_box_snapshot to permanently remove resources in Hetzner MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why hetzner_rollback_storage_box_snapshot needs a policy

Rolling back to a snapshot irreversibly overwrites the current state of the Storage Box, permanently destroying all data written after the snapshot was taken. This is a classic destructive operation with potentially catastrophic data loss impact.

From the tool's definition 'Roll a Storage Box back to a previous snapshot.' and '⚠️ DESTRUCTIVE: this overwrites the current state of the Storage Box. Any data written after the snapshot was taken will be lost.'

Questions about hetzner_rollback_storage_box_snapshot

What does the hetzner_rollback_storage_box_snapshot tool do? +

Roll a Storage Box back to a previous snapshot. ⚠️ DESTRUCTIVE: this overwrites the current state of the Storage Box. Any data written after the snapshot was taken will be lost. The \. It is categorised as a Destructive tool in the Hetzner MCP Server 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 hetzner_rollback_storage_box_snapshot? +

Register the Hetzner MCP Server MCP server in PolicyLayer and add a rule for hetzner_rollback_storage_box_snapshot: 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 Hetzner MCP Server. Nothing to install.

What risk level is hetzner_rollback_storage_box_snapshot? +

hetzner_rollback_storage_box_snapshot 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 hetzner_rollback_storage_box_snapshot? +

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

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

hetzner_rollback_storage_box_snapshot is provided by the Hetzner MCP Server MCP server (jurislm/hetzner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.