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 commit financial operations through Timeweb, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| 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 Critical
This tool updates a domain registration/renewal/transfer request and specifies payment source, which directly commits financial obligations (paying from balance or issuing an invoice). This falls under Financial as it involves spending money or creating payment obligations.
From the tool's definition указывая источник оплаты: use (с баланса), invoice (платёжка), free (бесплатный трансфер), bonus
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:
Any call to update_domain_request is blocked until a human approves it. The rest of the server keeps working.
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 Financial tool in the Timeweb MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
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 Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
Across the catalogue