dns_restore_snapshot

Restore a DNS snapshot for a domain.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/dns-restore-snapshot.md

WHAT IT DOES

What dns_restore_snapshot does on Hostinger

AI agents use dns_restore_snapshot to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.

RISK

Why dns_restore_snapshot is rated Medium

This tool restores DNS records from a snapshot, which is a reversible write operation that modifies live DNS configuration. While the snapshot mechanism suggests the change can theoretically be undone by restoring a different snapshot, the immediate effect is to overwrite current DNS settings—a significant modification to critical infrastructure.

From the tool's definition Tool is named 'dns_restore_snapshot' and described as 'Restore a DNS snapshot for a domain.' The action of restoring a snapshot modifies DNS records, which are critical infrastructure for domain routing and email delivery.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dns_restore_snapshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dns_restore_snapshot, this is the rule to start with:

dns_restore_snapshot Rate-limited

dns_restore_snapshot stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dns_restore_snapshot": {
      "limits": [
        {
          "counter": "dns_restore_snapshot_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about dns_restore_snapshot

What does the dns_restore_snapshot tool do? +

Restore a DNS snapshot for a domain. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dns_restore_snapshot? +

Register the Hostinger MCP server in PolicyLayer and add a rule for dns_restore_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 Hostinger. Nothing to install.

What risk level is dns_restore_snapshot? +

dns_restore_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dns_restore_snapshot? +

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

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

dns_restore_snapshot is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →