DNS_restoreDNSSnapshotV1
Restore DNS zone to the selected snapshot. Use this endpoint to revert domain DNS to a previous configuration.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/dns-restorednssnapshotv1.md
What DNS_restoreDNSSnapshotV1 does on Hostinger Api
AI agents use DNS_restoreDNSSnapshotV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name |
snapshotId | integer | Yes | Snapshot ID |
Parameters from the server's own tool schema.
Why DNS_restoreDNSSnapshotV1 is rated Medium
This tool restores a DNS zone to a previous snapshot, effectively overwriting the current DNS configuration. While it is a restoration/rollback operation (which implies the current state is overwritten), it uses a stored snapshot so the action is technically reversible (you could restore another snapshot). The most severe applicable category is Write, as it modifies DNS records.
From the tool's definition Restore DNS zone to the selected snapshot. Use this endpoint to revert domain DNS to a previous configuration.
Attacks that exploit this kind of access
The rule that runs DNS_restoreDNSSnapshotV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For DNS_restoreDNSSnapshotV1, this is the rule to start with:
DNS_restoreDNSSnapshotV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every DNS_restoreDNSSnapshotV1 call is checked against it from then on.
Questions about DNS_restoreDNSSnapshotV1
Restore DNS zone to the selected snapshot. Use this endpoint to revert domain DNS to a previous configuration. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
DNS_restoreDNSSnapshotV1 accepts 2 parameters: domain, snapshotId. Required: domain, snapshotId. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for DNS_restoreDNSSnapshotV1: 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 Api. Nothing to install.
DNS_restoreDNSSnapshotV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the DNS_restoreDNSSnapshotV1 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.
Set action: deny in the PolicyLayer policy for DNS_restoreDNSSnapshotV1. 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.
DNS_restoreDNSSnapshotV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue