DNS_getDNSSnapshotV1

Retrieve particular DNS snapshot with contents of DNS zone records. Use this endpoint to view historical DNS configurations for domains.

SERVERHostinger Api SOURCEhostinger-api-mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/dns-getdnssnapshotv1.md

WHAT IT DOES

What DNS_getDNSSnapshotV1 does on Hostinger Api

AI agents call DNS_getDNSSnapshotV1 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
`snapshotId`	integer	Yes	Snapshot ID

Parameters from the server's own tool schema.

RISK

Why DNS_getDNSSnapshotV1 is rated Low

This tool retrieves and queries historical DNS snapshot data. It has no side effects—it does not create, modify, delete, or execute any operations. The purpose is informational (viewing historical configurations), making it a Read category tool with low severity since it only exposes existing DNS configuration history.

From the tool's definition Tool name 'DNS_getDNSSnapshotV1' and description 'Retrieve particular DNS snapshot' indicate a retrieval operation. The phrase 'view historical DNS configurations' confirms read-only access to DNS data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

DNS_getDNSSnapshotV1 Allowed

DNS_getDNSSnapshotV1 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_getDNSSnapshotV1": {}
  }
}

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

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

FAQ

Questions about DNS_getDNSSnapshotV1

What does the DNS_getDNSSnapshotV1 tool do? +

Retrieve particular DNS snapshot with contents of DNS zone records. Use this endpoint to view historical DNS configurations for domains. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

What parameters does DNS_getDNSSnapshotV1 accept? +

DNS_getDNSSnapshotV1 accepts 2 parameters: domain, snapshotId. Required: domain, snapshotId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on DNS_getDNSSnapshotV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for DNS_getDNSSnapshotV1: 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.

What risk level is DNS_getDNSSnapshotV1? +

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

Can I rate-limit DNS_getDNSSnapshotV1? +

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

Set action: deny in the PolicyLayer policy for DNS_getDNSSnapshotV1. 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_getDNSSnapshotV1? +

DNS_getDNSSnapshotV1 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.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

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