DNS_updateDNSRecordsV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What DNS_updateDNSRecordsV1 does on Hostinger Api

AI agents use DNS_updateDNSRecordsV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

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.

RISK

Why DNS_updateDNSRecordsV1 is rated Medium

This tool modifies DNS records reversibly—updates and additions can be undone by subsequent updates or overwrites. While DNS changes have significant blast radius (domain availability, email routing, security), the changes are not permanent/irreversible like deletions. Categorized as Write rather than Execute because it directly modifies data state rather than triggering external operations.

From the tool's definition Tool name 'DNS_updateDNSRecordsV1' and description states 'Update DNS records' and 'modify domain DNS configuration'. The `overwrite` parameter allows replacing existing records, indicating reversible modification of DNS configuration data.

Risk signalsAccepts raw HTML/template content (zone[].records[].content)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

DNS_updateDNSRecordsV1 Rate-limited

DNS_updateDNSRecordsV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "DNS_updateDNSRecordsV1": {
      "limits": [
        {
          "counter": "dns_updatednsrecordsv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_updateDNSRecordsV1 call is checked against it from then on.

FAQ

Questions about DNS_updateDNSRecordsV1

What does the DNS_updateDNSRecordsV1 tool do? +

Update DNS records for the selected domain. Using overwrite = true will replace existing records with the provided ones. Otherwise existing records will be updated and new records will be added. Use this endpoint to modify domain DNS configuration. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does DNS_updateDNSRecordsV1 accept? +

DNS_updateDNSRecordsV1 accepts 3 parameters: zone, domain, overwrite. Required: zone, domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on DNS_updateDNSRecordsV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for DNS_updateDNSRecordsV1: 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_updateDNSRecordsV1? +

DNS_updateDNSRecordsV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit DNS_updateDNSRecordsV1? +

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

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

DNS_updateDNSRecordsV1 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

Govern customer-ops agents →Argument validation →Scoped token →