update_dns_record

Обновляет существующую DNS-запись по ID. Использует API v2. Нужно передать тип записи и новые поля.

SERVERTimeweb SOURCEtimeweb-mcp

Medium RISK CLASS

Category Write

Parameters 123 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What update_dns_record does on Timeweb

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

Parameter	Type	Required	Description
`ttl`	number	—	Новый TTL в секундах
`fqdn`	string	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - полное имя домена
`host`	string	—	SRV: хост сервиса
`port`	number	—	SRV: порт
`type`	string	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - тип DNS-записи
`value`	string	—	Новое значение DNS-записи
`app_id`	number	—	ID приложения App Platform
`service`	string	—	SRV: имя сервиса
`priority`	number	—	Приоритет (MX, SRV)
`protocol`	string	—	SRV: протокол
`record_id`	number	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID DNS-записи для обновления
`subdomain`	string	—	Имя поддомена (только префикс)

Parameters from the server's own tool schema.

RISK

Why update_dns_record is rated Medium

This tool modifies DNS records which are critical infrastructure settings. While reversible (Write category, not Destructive), misconfiguration could redirect traffic, block services, or enable phishing attacks. Severity is high due to blast radius affecting domain/service availability and potential for malicious redirects.

From the tool's definition Tool name 'update_dns_record' and description 'Обновляет существующую DNS-запись' (Updates existing DNS record) indicate modification of DNS configuration data.

Risk signalsAccepts URL/endpoint input (host) · High parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_dns_record safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_dns_record, this is the rule to start with:

update_dns_record Rate-limited

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

FAQ

Questions about update_dns_record

What does the update_dns_record tool do? +

Обновляет существующую DNS-запись по ID. Использует API v2. Нужно передать тип записи и новые поля. It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_dns_record accept? +

update_dns_record accepts 12 parameters: ttl, fqdn, host, port, type, value, app_id, service, priority, protocol, record_id, subdomain. Required: fqdn, type, record_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_dns_record? +

Register the Timeweb MCP server in PolicyLayer and add a rule for update_dns_record: 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 Timeweb. Nothing to install.

What risk level is update_dns_record? +

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

Can I rate-limit update_dns_record? +

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

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

update_dns_record is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Timeweb, and thousands of servers like it.

This server

All 245 Timeweb tools →

Across the catalogue

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

Guides

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