add_domain
Добавляет уже зарегистрированный в другом месте домен на аккаунт Timeweb Cloud для управления DNS и name-серверами. Не выполняет регистрацию — для регистрации используй create_domain_request.
This record as markdown: /tools/timeweb-mcp/add-domain.md
What add_domain does on Timeweb
AI agents use add_domain 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 |
|---|---|---|---|
fqdn | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - полное имя домена, который уже зарегистрирован у другого регистратора и его нужно добавить на аккаунт |
Parameters from the server's own tool schema.
Why add_domain is rated Medium
This tool creates a new association between an external domain and the user's Timeweb Cloud account, modifying account state by adding a manageable domain resource. It does not delete or execute arbitrary code, but it does persistently modify the account configuration.
From the tool's definition Tool name 'add_domain' and description states it 'adds an already-registered domain to the Timeweb Cloud account for DNS and nameserver management.' The verb 'добавляет' (adds) and the action of associating a domain resource with an account constitute a…
Attacks that exploit this kind of access
The rule that runs add_domain 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 add_domain, this is the rule to start with:
add_domain 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every add_domain call is checked against it from then on.
Questions about add_domain
Добавляет уже зарегистрированный в другом месте домен на аккаунт Timeweb Cloud для управления DNS и name-серверами. Не выполняет регистрацию — для регистрации используй create_domain_request. 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.
add_domain accepts 1 parameter: fqdn. Required: fqdn. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb MCP server in PolicyLayer and add a rule for add_domain: 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.
add_domain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_domain 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.
Set action: deny in the PolicyLayer policy for add_domain. 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.
add_domain 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.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue