create_dns_record

Создаёт DNS-запись (A, AAAA, TXT, CNAME, MX, SRV) для домена или поддомена. Использует API v2. Для SRV нужны host/port/service/protocol вместо value.

SERVERTimeweb SOURCEtimeweb-mcp

Medium RISK CLASS

Category Write

Parameters 112 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What create_dns_record does on Timeweb

AI agents use create_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) в секундах, например 600
`fqdn`	string	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - полное имя домена или поддомена, к которому добавить запись
`host`	string	—	SRV: каноническое имя хоста, предоставляющего сервис
`port`	number	—	SRV: порт сервиса
`type`	string	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - тип DNS-записи: A, AAAA, TXT, CNAME, MX, SRV
`value`	string	—	Значение DNS-записи. Для A — IPv4, AAAA — IPv6, TXT/CNAME/MX — строка. Для SRV не используется (см. host/port/service/protocol).
`app_id`	number	—	ID приложения в App Platform (для A-записи с привязкой к app)
`service`	string	—	SRV: имя сервиса, например _sip
`priority`	number	—	Приоритет (для MX и SRV записей)
`protocol`	string	—	SRV: протокол, например _TCP или _UDP
`subdomain`	string	—	Имя поддомена (только префикс, без основного домена)

Parameters from the server's own tool schema.

RISK

Why create_dns_record is rated Medium

An AI agent can call create_dns_record faster than any human can review: one bad instruction and it creates or modifies resources in Timeweb by the hundred, each call as confident as the last.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_dns_record Rate-limited

create_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": {
    "create_dns_record": {
      "limits": [
        {
          "counter": "create_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 create_dns_record call is checked against it from then on.

FAQ

Questions about create_dns_record

What does the create_dns_record tool do? +

Создаёт DNS-запись (A, AAAA, TXT, CNAME, MX, SRV) для домена или поддомена. Использует API v2. Для SRV нужны host/port/service/protocol вместо value. 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 create_dns_record accept? +

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

How do I enforce a policy on create_dns_record? +

Register the Timeweb MCP server in PolicyLayer and add a rule for create_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 create_dns_record? +

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

Can I rate-limit create_dns_record? +

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

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

create_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 →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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