DNS_getDNSRecordsV1
Retrieve DNS zone records for a specific domain. Use this endpoint to view current DNS configuration for domain management.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/dns-getdnsrecordsv1.md
What DNS_getDNSRecordsV1 does on Hostinger Api
AI agents call DNS_getDNSRecordsV1 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 |
|---|---|---|---|
domain | string | Yes | Domain name |
Parameters from the server's own tool schema.
Why DNS_getDNSRecordsV1 is rated Low
This tool retrieves and reads existing DNS records without creating, modifying, deleting, or executing any actions. It is a straightforward read operation used for viewing current configuration state. The blast radius of misuse is minimal — an attacker could only discover DNS configuration details, which may facilitate further attacks but does not directly cause harm on its own.
From the tool's definition Tool name contains 'get' and description states 'Retrieve DNS zone records' and 'view current DNS configuration' — these are query operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs DNS_getDNSRecordsV1 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_getDNSRecordsV1, this is the rule to start with:
DNS_getDNSRecordsV1 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_getDNSRecordsV1 call is checked against it from then on.
Questions about DNS_getDNSRecordsV1
Retrieve DNS zone records for a specific domain. Use this endpoint to view current DNS configuration for domain management. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
DNS_getDNSRecordsV1 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_getDNSRecordsV1: 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_getDNSRecordsV1 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_getDNSRecordsV1 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_getDNSRecordsV1. 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_getDNSRecordsV1 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