dns_validate_records

Validate DNS records before applying them.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What dns_validate_records does on Hostinger

AI agents call dns_validate_records to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why dns_validate_records is rated Low

This tool retrieves and validates existing or proposed DNS records to verify correctness before they are applied. Validation is a read-only operation that checks state without creating, modifying, or deleting records. It has minimal blast radius—worst case, an AI agent receives incorrect validation results, but cannot cause system damage.

From the tool's definition Tool name 'dns_validate_records' and description 'Validate DNS records before applying them' indicate a validation/checking operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dns_validate_records Allowed

dns_validate_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dns_validate_records": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about dns_validate_records

What does the dns_validate_records tool do? +

Validate DNS records before applying them. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dns_validate_records? +

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

dns_validate_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dns_validate_records? +

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

Set action: deny in the PolicyLayer policy for dns_validate_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_validate_records? +

dns_validate_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 →

Across the catalogue

validate_inputs on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →