list_dedicated_servers

Возвращает список всех выделенных (dedicated) серверов аккаунта: ID, имя, статус (installing/installed/on/off), локация, CPU/RAM/HDD описания, IPv4/IPv6, цена. Используй перед операциями над выделенным сервером, чтобы получить его ID.

SERVERTimeweb SOURCEtimeweb-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/timeweb-mcp/list-dedicated-servers.md

WHAT IT DOES

What list_dedicated_servers does on Timeweb

AI agents call list_dedicated_servers 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.

RISK

Why list_dedicated_servers is rated Low

This is a straightforward list/query operation that retrieves existing resource metadata from the account without side effects. It is informational and read-only, supporting other operations but not itself modifying state. The low severity reflects minimal risk if an AI misuses it—worst case is information disclosure about server inventory.

From the tool's definition Tool description uses 'Возвращает список' (returns a list) and 'получить' (get), indicating data retrieval. Lists dedicated server properties (ID, name, status, location, specs, IPs, price) with no modification, deletion, or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_dedicated_servers 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_dedicated_servers, this is the rule to start with:

list_dedicated_servers Allowed

list_dedicated_servers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_dedicated_servers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every list_dedicated_servers call is checked against it from then on.

FAQ

Questions about list_dedicated_servers

What does the list_dedicated_servers tool do? +

How do I enforce a policy on list_dedicated_servers? +

Register the Timeweb MCP server in PolicyLayer and add a rule for list_dedicated_servers: 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.

What risk level is list_dedicated_servers? +

list_dedicated_servers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_dedicated_servers? +

Yes. Add a rate_limit block to the list_dedicated_servers 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.

How do I block list_dedicated_servers completely? +

Set action: deny in the PolicyLayer policy for list_dedicated_servers. 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.

What MCP server provides list_dedicated_servers? +

list_dedicated_servers 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.

KEEP EXPLORING

More on Timeweb, and thousands of servers like it.

This server

All 245 Timeweb tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →