dns_update_records

Update/replace DNS records for a domain.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What dns_update_records does on Hostinger

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

RISK

Why dns_update_records is rated Medium

DNS record updates are reversible write operations that modify domain routing and services but do not permanently delete data. However, severity is high because misconfiguration can cause severe business impact (service outages, email failures, security vulnerabilities). An AI agent with this capability could redirect traffic, intercept communications, or disable services if given incorrect instructions.

From the tool's definition Tool name 'dns_update_records' and description 'Update/replace DNS records for a domain' explicitly indicate modification of DNS configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dns_update_records Rate-limited

dns_update_records 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_update_records": {
      "limits": [
        {
          "counter": "dns_update_records_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, apply this rule, and every dns_update_records call is checked against it from then on.

FAQ

Questions about dns_update_records

What does the dns_update_records tool do? +

Update/replace DNS records for a domain. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dns_update_records? +

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

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

Can I rate-limit dns_update_records? +

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

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

dns_update_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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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