list_dns_records
Возвращает все пользовательские DNS-записи домена: ID, тип (A/AAAA/CNAME/MX/TXT/SRV), значение, TTL, поддомен, priority.
This record as markdown: /tools/timeweb-mcp/list-dns-records.md
What list_dns_records does on Timeweb
AI agents call list_dns_records 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 |
|---|---|---|---|
fqdn | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - полное имя домена |
Parameters from the server's own tool schema.
Why list_dns_records is rated Low
This tool queries and returns DNS record information without side effects. It is a read-only operation that retrieves existing data. The low severity reflects minimal blast radius—an AI agent misusing this tool would only gain DNS configuration visibility, not enable unauthorized changes or external impacts.
From the tool's definition Tool name 'list_dns_records' and description 'Возвращает все пользовательские DNS-записи домена' (Returns all custom DNS records of a domain) with retrieval of ID, type, value, TTL, subdomain, and priority. No modification, deletion, or execution is performed.
Attacks that exploit this kind of access
The rule that runs list_dns_records 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 list_dns_records, this is the rule to start with:
list_dns_records 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 list_dns_records call is checked against it from then on.
Questions about list_dns_records
Возвращает все пользовательские DNS-записи домена: ID, тип (A/AAAA/CNAME/MX/TXT/SRV), значение, TTL, поддомен, priority. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
list_dns_records 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 list_dns_records: 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.
list_dns_records 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 list_dns_records 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 list_dns_records. 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.
list_dns_records 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