update_domain_request
Обновляет заявку на регистрацию/продление/трансфер, указывая источник оплаты: use (с баланса), invoice (платёжка), free (бесплатный трансфер), bonus.
This record as markdown: /tools/timeweb-mcp/update-domain-request.md
What update_domain_request does on Timeweb
AI agents use update_domain_request 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 |
|---|---|---|---|
bonus_id | number | — | ID бонуса (ОБЯЗАТЕЛЕН для bonus) |
payer_id | number | — | ID плательщика (ОБЯЗАТЕЛЕН для invoice) |
auth_code | string | — | Код авторизации переноса (ОБЯЗАТЕЛЕН для free/transfer) |
person_id | number | — | ID администратора домена |
request_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID заявки для оплаты/обновления |
money_source | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - способ оплаты: use (с баланса), invoice (платёжка), free (только для transfer), bonus |
payment_type | string | — | Тип платёжной системы (ОБЯЗАТЕЛЕН для invoice) |
Parameters from the server's own tool schema.
Why update_domain_request is rated Medium
An AI agent can call update_domain_request 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.
Attacks that exploit this kind of access
The rule that runs update_domain_request 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_domain_request, this is the rule to start with:
update_domain_request 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 update_domain_request call is checked against it from then on.
Questions about update_domain_request
Обновляет заявку на регистрацию/продление/трансфер, указывая источник оплаты: use (с баланса), invoice (платёжка), free (бесплатный трансфер), bonus. 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.
update_domain_request accepts 7 parameters: bonus_id, payer_id, auth_code, person_id, request_id, money_source, payment_type. Required: request_id, money_source. 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 update_domain_request: 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.
update_domain_request 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 update_domain_request 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 update_domain_request. 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.
update_domain_request 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