DNS_deleteDNSRecordsV1
Delete DNS records for the selected domain. To filter which records to delete, add the name of the record and type to the filter. Multiple filters can be provided with single request. If you have multiple records with the same name and type, and you want to delete only part of them, refer to the ...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/dns-deletednsrecordsv1.md
What DNS_deleteDNSRecordsV1 does on Hostinger Api
AI agents call DNS_deleteDNSRecordsV1 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 |
|---|---|---|---|
domain | string | Yes | Domain name |
Parameters from the server's own tool schema.
Why DNS_deleteDNSRecordsV1 is rated Critical
This tool irreversibly deletes DNS records, which cannot be undone and would cause immediate service disruption if the wrong records are deleted. DNS record deletion is a destructive operation that affects domain functionality and is not reversible through the tool itself.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete DNS records for the selected domain.' The function performs irreversible deletion of DNS records without recovery mechanism mentioned.
Attacks that exploit this kind of access
The rule that runs DNS_deleteDNSRecordsV1 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_deleteDNSRecordsV1, this is the rule to start with:
DNS_deleteDNSRecordsV1 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_deleteDNSRecordsV1 call is checked against it from then on.
Questions about DNS_deleteDNSRecordsV1
Delete DNS records for the selected domain. To filter which records to delete, add the name of the record and type to the filter. Multiple filters can be provided with single request. If you have multiple records with the same name and type, and you want to delete only part of them, refer to the Update zone records endpoint. Use this endpoint to remove specific DNS records from domains. 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_deleteDNSRecordsV1 accepts 1 parameter: domain. 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_deleteDNSRecordsV1: 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_deleteDNSRecordsV1 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_deleteDNSRecordsV1 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_deleteDNSRecordsV1. 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_deleteDNSRecordsV1 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