get_domain_request
Возвращает детали заявки на регистрацию/продление/трансфер по её ID.
This record as markdown: /tools/timeweb-mcp/get-domain-request.md
What get_domain_request does on Timeweb
AI agents call get_domain_request to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
request_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID заявки |
Parameters from the server's own tool schema.
Why get_domain_request is rated Low
The tool retrieves and returns existing data about a domain request without modifying, executing, or deleting anything. It has no side effects and is a standard read operation. The blast radius of misuse is minimal—an attacker gains visibility into request metadata but cannot manipulate domain operations or financial resources directly through this tool alone.
From the tool's definition Tool name is 'get_domain_request' and description states 'Возвращает детали заявки' (Returns details of a request) — this is a retrieval operation that queries domain registration/renewal/transfer request details by ID.
Attacks that exploit this kind of access
The rule that runs get_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 get_domain_request, this is the rule to start with:
get_domain_request is read-only, so it stays allowed. 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 get_domain_request call is checked against it from then on.
Questions about get_domain_request
Возвращает детали заявки на регистрацию/продление/трансфер по её ID. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
get_domain_request accepts 1 parameter: request_id. Required: request_id. 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 get_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.
get_domain_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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