dns_reset_records

Reset all DNS records for a domain to defaults.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/dns-reset-records.md

WHAT IT DOES

What dns_reset_records does on Hostinger

AI agents call dns_reset_records to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why dns_reset_records is rated Critical

This tool irreversibly overwrites all DNS records for a domain, which cannot be undone without manual restoration. An AI agent misusing this could take a domain offline, break email delivery, disrupt SSL/TLS certificates, and cause immediate service outages. The blast radius is organization-wide and affects all services relying on DNS resolution for that domain.

From the tool's definition Tool name 'dns_reset_records' and description 'Reset all DNS records for a domain to defaults' indicates irreversible deletion/overwriting of all DNS records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dns_reset_records 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_reset_records, this is the rule to start with:

dns_reset_records Hidden

dns_reset_records is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "dns_reset_records"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about dns_reset_records

What does the dns_reset_records tool do? +

Reset all DNS records for a domain to defaults. It is categorised as a Destructive tool in the Hostinger 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 dns_reset_records? +

Register the Hostinger MCP server in PolicyLayer and add a rule for dns_reset_records: 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_reset_records? +

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

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

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

dns_reset_records 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 → Critical-risk tools on this server →

Across the catalogue

team_manager_reset on Team Manager MCP →delete_dns_record on cPanel MCP Server →reset_mcp_runtime_metrics on 0xpdf → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →