DNS_resetDNSRecordsV1
Reset DNS zone to the default records. Use this endpoint to restore domain DNS to original configuration.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/dns-resetdnsrecordsv1.md
What DNS_resetDNSRecordsV1 does on Hostinger Api
AI agents call DNS_resetDNSRecordsV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
sync | boolean | — | Determines if operation should be run synchronously |
domain | string | Yes | Domain name |
reset_email_records | boolean | — | Determines if email records should be reset |
whitelisted_record_types | array | — | Specifies which record types to not reset |
Parameters from the server's own tool schema.
Why DNS_resetDNSRecordsV1 is rated Critical
This tool destroys custom DNS configurations by resetting them to defaults. While not a deletion in the strict sense, it irreversibly overwrites live DNS records, preventing legitimate DNS customizations from being recoverable without external intervention. This is a destructive operation that can break email delivery, website routing, and other DNS-dependent services.
From the tool's definition "Reset DNS zone to the default records" and "restore domain DNS to original configuration" — these operations overwrite existing DNS records with defaults, which irreversibly replaces the current DNS configuration and cannot be undone without manual…
Attacks that exploit this kind of access
The rule that runs DNS_resetDNSRecordsV1 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_resetDNSRecordsV1, this is the rule to start with:
DNS_resetDNSRecordsV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every DNS_resetDNSRecordsV1 call is checked against it from then on.
Questions about DNS_resetDNSRecordsV1
Reset DNS zone to the default records. Use this endpoint to restore domain DNS to original configuration. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
DNS_resetDNSRecordsV1 accepts 4 parameters: sync, domain, reset_email_records, whitelisted_record_types. Required: domain. 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_resetDNSRecordsV1: 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_resetDNSRecordsV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the DNS_resetDNSRecordsV1 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_resetDNSRecordsV1. 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_resetDNSRecordsV1 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.
Across the catalogue