dns_get_records

Get all DNS records for a domain.

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-get-records.md

WHAT IT DOES

What dns_get_records does on Hostinger

AI agents call dns_get_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_get_records is rated Low

This tool retrieves DNS records without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security risk—DNS records are typically considered low-sensitivity configuration data, and unauthorized read access has limited immediate blast radius compared to write or destructive operations.

From the tool's definition Tool name 'dns_get_records' and description 'Get all DNS records for a domain' indicate retrieval of existing data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dns_get_records Allowed

dns_get_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_get_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_get_records call is checked against it from then on.

FAQ

Questions about dns_get_records

What does the dns_get_records tool do? +

Get all DNS records for a domain. 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_get_records? +

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

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

Can I rate-limit dns_get_records? +

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

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

dns_get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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