DNS_validateDNSRecordsV1
Validate DNS records prior to update for the selected domain. If the validation is successful, the response will contain 200 Success code. If there is validation error, the response will fail with 422 Validation error code. Use this endpoint to verify DNS record validity before applying changes.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/dns-validatednsrecordsv1.md
What DNS_validateDNSRecordsV1 does on Hostinger Api
AI agents call DNS_validateDNSRecordsV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
zone | array | Yes | zone parameter |
domain | string | Yes | Domain name |
overwrite | boolean | — | If `true`, resource records (RRs) matching name and type will be deleted and new RRs will be created, otherwise resource records' ttl's are updated and new reco |
Parameters from the server's own tool schema.
Why DNS_validateDNSRecordsV1 is rated Low
This tool only reads and validates DNS records without creating, modifying, or deleting any data. It returns validation status codes (200 Success or 422 Validation error) to inform the user whether records are valid, with no side effects. This is a classic Read operation—it queries and checks data without altering state.
From the tool's definition Tool name contains 'validate' and description states 'Validate DNS records prior to update' and 'verify DNS record validity before applying changes'. The tool performs validation/verification without making any modifications to DNS records or other data.
Risk signalsAccepts raw HTML/template content (zone[].records[].content)
Attacks that exploit this kind of access
The rule that runs DNS_validateDNSRecordsV1 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_validateDNSRecordsV1, this is the rule to start with:
DNS_validateDNSRecordsV1 is read-only, so it stays allowed. 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_validateDNSRecordsV1 call is checked against it from then on.
Questions about DNS_validateDNSRecordsV1
Validate DNS records prior to update for the selected domain. If the validation is successful, the response will contain 200 Success code. If there is validation error, the response will fail with 422 Validation error code. Use this endpoint to verify DNS record validity before applying changes. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
DNS_validateDNSRecordsV1 accepts 3 parameters: zone, domain, overwrite. Required: zone, 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_validateDNSRecordsV1: 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_validateDNSRecordsV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the DNS_validateDNSRecordsV1 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_validateDNSRecordsV1. 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_validateDNSRecordsV1 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